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

+51
View File
@@ -191,3 +191,54 @@ test('Mapillary can be omitted or replaced without changing catalog membership',
/Mapillary source/,
);
});
test('the catalog per engine: Cesium as before, Navara only what it can show', async (t) => {
const { APPLICATION_LAYER_DIRECTORY } = await import('./layers/directory.js');
const { createLayerAvailability, createRendererRegistry } =
await import('./layers/renderers.js');
const controller = new AbortController();
t.after(() => controller.abort());
const build = (options) =>
createApplicationCatalog({
sources: createStandaloneLayerSources(),
signal: controller.signal,
surface: fixtureSurface(controller.signal),
...options,
});
const cesium = build({});
// The directory is the catalog Cesium builds: ids, names and order.
assert.deepEqual(
cesium.layers.map(({ id, name }) => ({ id, name })),
APPLICATION_LAYER_DIRECTORY.map(({ id, name }) => ({ id, name })),
);
assert.equal(cesium.engineKind, 'cesium');
assert.deepEqual(cesium.unavailableMetadata, []);
assert.equal(cesium.availability.unavailable().length, 0);
const navara = build({ engineKind: 'navara' });
assert.equal(navara.layers.length, 0, 'no Navara renderers yet');
assert.equal(navara.unavailableMetadata.length, cesium.metadata.length);
assert.equal(navara.availability.engine, 'navara');
// With Navara renderers for two layers, only those are constructed, in
// catalog order, with their metadata.
const registry = createRendererRegistry();
registry.register('navara', {
satellites: () => ({}),
flights: () => ({}),
});
const subset = build({
engineKind: 'navara',
availability: createLayerAvailability('navara', { registry }),
});
assert.deepEqual(
subset.layers.map(({ id }) => id),
['flights', 'satellites'],
);
assert.deepEqual(
subset.metadata.map(({ id }) => id),
['flights', 'satellites'],
);
assert.ok(subset.unavailableMetadata.some(({ id }) => id === 'military'));
assert.equal(subset.get('military'), undefined);
});