{"version":"2.1.235","anchor":"command-queue-became-an-instance-with-a-subscribable-snapsho","canonical_anchor":"command-queue-became-an-instance-with-a-subscribable-snapsho","heading":"Command queue became an instance with a subscribable snapshot, and commands can be 'passive'","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/command-queue-became-an-instance-with-a-subscribable-snapsho","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Command queue became an instance with a subscribable snapshot, and commands can be 'passive'\n\nCommand queue is now an instance with a subscribable snapshot, and commands can be marked 'passive'\n\n**Unclear.** Whether this change is active for a given account depends on `tengu_hover_rest`, which has not yet been read under this release.\n\nModule-level command-queue singletons were replaced by an accessor object. Consumers now subscribe to queue changes via `subscribe`\/`getCommandQueueSnapshot` and call `recheckCommandQueue()` instead of a free-standing function.\n\nCommands gained a `passive` marker with predicates distinguishing passive from non-passive queued commands, and the Esc\/cancel handler now returns a boolean indicating whether it consumed the key, with `vOe(..., { passive: !0 })` used for passive drains.\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.235; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}