Files
gods-eye-view/src/rightRailPolicy.js
T
Manjunath PaparajuandSameh Khamis 0a6fd5f43f Make Space Missions an ordinary layer with its own panel
Space Missions no longer runs as a Context mode. The launches layer owns
its Satellites dependency, including the rule that a Satellites off
asked for after Space Missions was switched on ends it (request order
decides), and a small controller connects the layer to its own panel and
store. Context no longer isolates, snapshots or restores Space Missions
or Satellites, so Contacts and Space Missions run together in either
order, and scene playback no longer exits an isolating mode. Settled by
the owner: Contacts leaves Satellites as it is, and only a person's or
voice Satellites off ends Space Missions; a scene, story, preset or
other programmatic off does not.

Turning the layer on by hand or by voice, choosing it at first run, or
picking a mission on the globe opens the Space Missions panel, and on a
phone its Missions sheet. Asking voice to open the panel while the layer
is off is refused with a reason, and voice never opens it while the
Cockpit owns the screen. With no Context mode on, a voice Context off
switches Space Missions off. A failed Satellites restore no longer cuts
the layer's teardown short. Mission labels on the globe select their
mission. The layer names a failed first index load itself, so the
Context toast no longer imports Space Missions code.

Also carries the satellites request ordering and
DataLayerManager.waitForLayerIdle, the share token for the panel, voice
panel ids, Cockpit folding the panel away and the phone tab ellipsis.
The panel shares the rail gutters and hover border of the other side
panels.

On top of the Omnibar: "open space missions panel" reaches the new
panel, and Open Context no longer answers to "missions".

Co-authored-by: Sameh Khamis <[email protected]>
2026-11-18 16:03:51 -08:00

32 lines
1.2 KiB
JavaScript

const GLOBAL_CONTEXT_EXPLICIT_ACTIONS = new Set(['contacts', 'cockpit']);
/**
* Decide whether a completed action should reveal the Global Context panel.
* Expansion belongs only to an explicit, successful owner action. Restoring a
* session or replaying saved state must preserve the saved collapsed state,
* and a failed transition must leave the prior panel state untouched.
*
* Whether an aircraft is already selected is deliberately irrelevant: an
* explicit Cockpit action still reveals the context that supports that track.
*
* @param {object} input Action outcome and coordination state.
* @param {'contacts'|'cockpit'|string} input.action Completed action.
* @param {boolean} input.explicitUserAction Whether the user directly requested it.
* @param {boolean} input.succeeded Whether the requested transition completed.
* @param {boolean} [input.restoring=false] Whether saved/session state is being restored.
* @returns {boolean} Whether Global Context should be expanded.
*/
export function shouldExpandGlobalContextPanel({
action,
explicitUserAction,
succeeded,
restoring = false,
}) {
return Boolean(
GLOBAL_CONTEXT_EXPLICIT_ACTIONS.has(action) &&
explicitUserAction &&
succeeded &&
!restoring,
);
}