Under the hood
Useful1 Signal1
Query setup moved out of the main session view into an engine object.
What's wrong with this entry?
Anonymous. No account, no email.
What
Several hundred lines of query and tool-context setup in the REPL were replaced by a single binding step that hands the session, registries and callbacks to an engine object, and the fleet view's state became a store with methods. No behaviour change was identified, but almost every fleet and REPL key binding now goes through the store.
Details
- Fleet state is read through a snapshot getter and changed through named calls such as
setGroupPickIdx,abandonRespawnAttempt,nextRespawnAttemptandcloseResumePicker.
Evidence
abandonRespawnAttempt
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background REPL evaluations report back into the conversation
Both mention repl
-
v2.1.248
Prompt submission and composer state moved into dedicated controllers
Both mention repl
-
v2.1.248
Prompt input takes grouped objects and drops some handler guards
Both mention repl