OpenCode/Flight-Ops
2
0
Fork 0
Code Issues Pull Requests Actions Activity

Queue should be done by clicking "fly to...." on "on board" and by "Relocate" - it doesn't need dedicated input. #53

New Issue
Closed
opened 2026-09-20 15:06:07 +02:00 by kamilkrzywda · 1 comment
kamilkrzywda commented 2026-09-20 15:06:07 +02:00
Owner
Copy Link
Copy Source
No description provided.
kamilkrzywda commented 2026-09-21 02:20:01 +02:00
Author
Owner
Copy Link
Copy Source

Done — the dedicated queue input is gone; queuing now happens through the existing controls.

What changed (v0.32.0, PR #63, merge commit 4e585cbed11f9c11f56ee4711d9675a503cfff8d):

  • The per-cargo-row "Fly to {destination}" button on the On board list is now enabled in both states and routes by plane state: grounded → POST /api/planes/{id}/fly (one-click departure, as before), flying → POST /api/planes/{id}/queue (appends the leg; it auto-chains when the current leg lands).
  • The Relocate section's plane select now lists all planes (not just grounded ones) and applies the same rule — so you can extend a flying plane's route from Relocate too.
  • The dedicated "Add to queue" airport select + button in each on-board block was removed, along with its shared state. Queued leg rows (queue-leg-*) and their Cancel buttons are unchanged.
  • No API changes (all three endpoints — /fly, /queue, /queue/cancel — stay), no OpenAPI change; the map popup's "Relocate here" is untouched.

Tests: e2e/queue.spec.ts now adds its queued leg through the Relocate section instead of the removed control; e2e/two-planes.spec.ts seeds its extra leg via API (per-plane independence + auto-chain still covered). Local: tsc clean, vitest 327/32 files, playwright list 52 tests in 14 files. CI green on PR #63.

Deployed to https://flight.dev.kkhost.pl (verified /api/version = 0.32.0 + root HTTP 200).

Done — the dedicated queue input is gone; queuing now happens through the existing controls. **What changed (v0.32.0, PR #63, merge commit `4e585cbed11f9c11f56ee4711d9675a503cfff8d`):** - The per-cargo-row **"Fly to {destination}"** button on the On board list is now enabled in both states and routes by plane state: grounded → `POST /api/planes/{id}/fly` (one-click departure, as before), flying → `POST /api/planes/{id}/queue` (appends the leg; it auto-chains when the current leg lands). - The **Relocate** section's plane select now lists *all* planes (not just grounded ones) and applies the same rule — so you can extend a flying plane's route from Relocate too. - The dedicated "Add to queue" airport select + button in each on-board block was removed, along with its shared state. Queued leg rows (`queue-leg-*`) and their Cancel buttons are unchanged. - No API changes (all three endpoints — /fly, /queue, /queue/cancel — stay), no OpenAPI change; the map popup's "Relocate here" is untouched. **Tests:** e2e/queue.spec.ts now adds its queued leg through the Relocate section instead of the removed control; e2e/two-planes.spec.ts seeds its extra leg via API (per-plane independence + auto-chain still covered). Local: tsc clean, vitest 327/32 files, playwright list 52 tests in 14 files. CI green on PR #63. Deployed to https://flight.dev.kkhost.pl (verified `/api/version` = 0.32.0 + root HTTP 200).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
kamilkrzywda (Kamil Krzywda) smysakowski
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: OpenCode/Flight-Ops#53