feat(app): layer catalog per engine

- src/app/layers/renderers.js: the layer renderer registry
  (registerLayerRenderers(engineKind, { [layerId]: factory }),
  rendererFor(layerId, engine), layerAvailableOn(layerId, engineKind)).
  Every application layer is registered for Cesium as CESIUM_BUILTIN (it
  still draws itself until its render/cesium.js); Navara factories come with
  the layer tasks. On it, the stable availability API phase 4 injects into
  its layer list: createLayerAvailability(engineKind) →
  { engine, isAvailable(id), available(), unavailable() } with { id, name }
  rows (src/app/layers/directory.js holds the ids and names in catalog
  order; a test keeps it equal to the constructed catalog).
- createApplicationCatalog({ engineKind, availability }) constructs only the
  layers the engine can show, in the same order (shared instances made
  once, on demand); the catalog carries `availability` and the others'
  metadata (`unavailableMetadata`). Cesium builds the same 30 layers in the
  same order as before; Navara builds none yet (no Navara renderers) - the
  standalone app now asks the catalog for it instead of making an empty one.
- catalogControlServices: a role whose layer the engine leaves out gets an
  empty stand-in (absentLayerControlServices folded in); any other missing
  layer is still a wiring error.
- LayerLifecycle(viewer, { engine }): every module call (init, enable,
  update, disable, destroy) gets { signal, engine } as its second argument;
  viewer is null on Navara.
- Links: a link that turns on layers this engine leaves out keeps them in
  the durable state (re-saved links carry them; back on Cesium they turn
  on) and activates nothing; a notice names them ("NOT ON THIS ENGINE · Kept
  in the link: …"). The Navara notice lists the engine's data layers from
  the registry.
- The dev launcher's CCTV wiring check matches the new catalog form.
This commit is contained in:
German Khokhlov committed 2026-10-16 22:07:55 +04:00
1 parent e1be2eac19
commit b0cbed081b
23 files changed
+826 -146

No files matched your search

+46
View File
@@ -2793,3 +2793,49 @@ test('explicit provider switches reach durable state without adopting unrelated
coordinator.destroy();
}
});
test('a link through an engine without some layers keeps their state and activates nothing', async () => {
// The Navara catalog: only satellites registered.
const manager = new DataLayerManager({});
const enabled = [];
manager.register(
fakeLayer('satellites', { enable: () => (enabled.push('satellites'), true) }),
);
manager.finalizeRegistrations(
LAYER_STATE_REGISTRY.filter(({ id }) => id === 'satellites'),
);
const shared = normalizeLayerState({
enabledLayerIds: ['flights', 'ais-live-vessels', 'satellites'],
});
const sink = shareSink();
const coordinator = new LayerStateCoordinator(manager, sink, {
storage: memoryStorage(),
});
const results = await coordinator.start({
shareLayerState: shared,
shareCreatedAtMs: 1_000,
});
assert.deepEqual(enabled, ['satellites'], 'only the registered layer runs');
const missing = results
.filter(({ phase, targetEnabled }) => phase === 'missing' && targetEnabled)
.map(({ layerId }) => layerId)
.sort();
assert.deepEqual(missing, ['ais-live-vessels', 'flights']);
// Re-saved (the link the user copies on Navara): the state is all there.
assert.deepEqual(
sink.provider().enabledLayerIds,
['ais-live-vessels', 'flights', 'satellites'],
);
// An explicit change of a layer that is here keeps the others too.
await manager.setEnabled('satellites', false, { origin: 'user' });
assert.deepEqual(sink.provider().enabledLayerIds, [
'ais-live-vessels',
'flights',
]);
// And back on Cesium the link turns them on.
const decoded = decodeLayerStateParams(
new URLSearchParams(encode(sink.provider())),
);
assert.deepEqual(decoded.enabledLayerIds, ['ais-live-vessels', 'flights']);
coordinator.destroy();
});