Handle OpChanges in TS backend calls #4508
Open
+120
−6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Luc-Mcgrady
added a commit
to Luc-Mcgrady/anki
that referenced
this pull request
Jan 24, 2026
------- Co-authored-by: Abdo <[email protected]>
Luc-Mcgrady
added a commit
to Luc-Mcgrady/anki
that referenced
this pull request
Jan 24, 2026
--------- Co-authored-by: Abdo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Most TS backend calls that return OpChanges are currently not reflected in UI undo status. This provides a generic solution to extract OpChanges from responses (with handling for nesting).
The
registerOperationHandlerTS function was also added to allow Svelte pages to register operation handlers and react to changes in other screens.This solution is already used in #4029 and will probably be useful for #4289