Don't pre-create stateChanges to avoid empty structures for no-op changes#506
Merged
Don't pre-create stateChanges to avoid empty structures for no-op changes#506
stateChanges to avoid empty structures for no-op changes#506Conversation
stateChanges: it results in empty structures for no-op changesstateChanges to avoid empty structures for no-op changes
tamirms
approved these changes
Aug 29, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
As part of #396 we allowed pre and post to both be
nil, but did not handle their JSON-side rendering. Since we preallocated thestateChangeslist, it would have empty structures in those cases despite thecontinue. By usingappend, we ensure only meaningful structures get rendered.Why
We should conform to our API contract and never have
type = "".Known limitations
n/a