chore: Undo recent changes to EngineService controller update handling
#21155
+21
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A recent PR (#17685) migrated to a new storage system for controller state. This change required additional state change subscriptions, but in the process of setting those up, the "update Redux" step ended up inside of the persistence handler.
This is not ideal because it's semantically confusing (updating Redux is not related to persistence, it's how we update the UI), and it means UI updates are now slightly delayed (
getPersistentStateis now called each update before the UI is updated).This PR reverts the changes to how Redux is updated when controller state changes without impacting the persistence handling.
Changelog
CHANGELOG entry: null
Related issues
N/A
Manual testing steps
N/A
Screenshots/Recordings
N/A
Pre-merge author checklist
Pre-merge reviewer checklist