mirror of
https://github.com/bilawalsidhu/gods-eye-view.git
synced 2026-11-17 16:52:20 +00:00
fix(launches): cancel mission flights on exit and name a failed index load
Review fixes on top of #1578: - Exiting Space Missions cancels the layer's own camera flights again (entry, roster preview, mission focus); only a flight navigation started after releaseCameraOwnership() runs on. - A failed first index load says so: "Space Missions unavailable: the mission index could not load. Try again later." on both the Context and Data Layers routes, instead of a generic transition toast. Translated. - Regression tests for both; docs and changelog describe the real feedback. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
1 parent
3cd7ed68aa
commit
13219828e3
22 files changed
+98
-16
No files matched your search
@@ -1,5 +1,4 @@
|
||||
- Space Missions no longer locks the workspace when its mission index fails to
|
||||
load. A 429, timeout or bad payload on `/api/launches` now rolls the entry
|
||||
back to the previous layers and camera view instead of leaving an empty,
|
||||
isolating mode, and the roster reads `30-DAY MISSION INDEX UNAVAILABLE`
|
||||
rather than loading forever (German, @gekh, #1578).
|
||||
load (429, timeout or bad payload): entry rolls back to the previous layers
|
||||
and camera view and a toast says the index could not load (German, @gekh,
|
||||
#1578).
|
||||
Reference in new issue
Block a user