quazardous/qdadm @quazardous/qdadm@2.15.0

on GitHub

Minor Changes

• 8619a4e: Per-entity punchline: new optional description on EntityManager — a one-liner explaining what the entity is, rendered as a muted subtitle under the list page title. useListPage picks it up automatically; override per page with the subtitle option (null suppresses it).
• dd100d7: Declare which entities your backend writes out of session, and qdadm routes its events to the right cache (#1888 lot C, reported in #1887). sse: { entities: ['runs', 'jobs'] } — or true / '*' for all — makes the stream's entity:{created,updated,deleted} frames (data: {"entity": "runs", "id": 42}) invalidate that entity's cache; the frame names are registered for you. Undeclared entities are ignored, since a stream carries more than entity mutations, with a one-off dev warning per entity so a dropped frame is never silent. The routing runs inside the front's security scope: an event for an entity the current user cannot read is dropped rather than refetched. LiveEntityRouter is transport-agnostic — its notify(entity, action, id) entry point takes a plain fact, so a WebSocket or a BroadcastChannel between two tabs attaches the same way SSE does.
• a22f012: A screen showing a live entity now follows changes made outside the session (#1888 lot D, reported in #1887). Invalidating marks a cache stale but repaints nothing, so a list already on screen kept its rows until the user navigated away and back — precisely the case a pushing backend exists for. useListPage and useEntityItemShowPage now reload themselves, with no page-level opt-in to forget: the gate is upstream, since only an entity declared in sse.entities ever produces a remote event. Each entity carries its own policy, pre-wired and overridable — live: { refresh: 'mounted' | false, coalesceMs: 300 } on the EntityManager, so a heavy logs list can drop its stale cache without refetching while runs refreshes on sight. A burst of events collapses into one reload; a detail page only reacts to its own record; and a list refreshing under someone mid-bulk-action keeps their selection, re-matched by key.
• 534512e: Remote changes now invalidate the list cache (#1888 lot B, reported in #1887). entity:data-invalidate carries a source marker, and an EntityManager receiving source: 'remote' for its own entity drops its list cache. Until now no subscriber cleared it: the parent-entity handler only fires for an entity's parents, and the own-entity handler is gated on asymmetric mode and only touched the detail cache — so an ordinary entity received nothing, and an app emitting the canonical signal kept serving a stale list while believing it had invalidated everything. Local mutations emit source: 'local' and are ignored by that handler, since the manager that mutated has already repaired its own cache: writes cost no extra refetch.
• e910984: SSE: the auth token may now be fetched asynchronously, and the kernel sse config can supply it (#1888 lot A, BookShepherd report #1887). EventSource accepts no headers, so the token rides in the query string and lands in access logs — apps that refuse to leak a durable credential there can now serve a short-lived, single-use ticket instead: getToken accepts () => string | null | Promise<string | null>, awaited before each connect. SSEConfig gains getToken (an explicit null sends no token at all), plus connectOnSignal / disconnectOnSignal passthrough — without them the async token was unreachable for anyone using the kernel's sse config rather than building an SSEBridge by hand. Purely additive: synchronous getToken implementations keep working unchanged. A connect that awaited its token now checks it has not been superseded before opening the connection, so a disconnect() or a second connect() during the fetch no longer resurrects a torn-down stream.
• 4a04f4d: Vendor pluralize as an internal ESM module and drop it from dependencies (#1454). qdadm no longer has any CJS transitive, so qdadmVitePlugin stops emitting optimizeDeps.include entirely — this fixes the unresolvable pluralize optimizer error for file:-linked consumers (npm install-links=false), where qdadm's deps are never installed at the consumer root. Consumers that added pluralize as a direct-dependency workaround can remove it.

Patch Changes

• a87ee80: Declare which parts of the API are stable and which are still moving (#1029). New docs/API_STABILITY.md defines three tiers operationally — stable is what the CI-enforced consumer-smoke fixture and the tutorial exercise, supported is documented and demo-exercised, experimental is marked in the source — and says what breaking each one costs. Five module entry points now carry @experimental JSDoc, visible in editor tooltips: chain/, deferred/, query/ (the executor classes only — the query object syntax is stable), kernel/SSEBridge, and gen/vite-plugin. Annotations and docs only; no API change.
• 2fbdaab: Fix: a live event naming an entity with no registered manager is dropped instead of throwing (#1888). Orchestrator.get() raises on an unknown name by design — to catch developer typos loudly — so the live router now checks has() first. A typo in sse.entities, or an entity whose module is lazily loaded, would otherwise have raised inside the signal bus on every frame the backend sent.
• c2946e6: Declare sass-embedded as an optional peerDependency and add it to every quick-start install line (#1514, aihoku feedback). qdadm ships raw .scss styles, so Vite consumers need a sass compiler — the requirement is now visible in metadata and docs instead of surfacing as a Preprocessor dependency "sass-embedded" not found overlay on first boot.
• Updated dependencies [e910984]
  • @quazardous/qdcore@1.1.0