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.
Fixes #3161
The bug was caused by the nextjs build step obfuscating all the names of the symbols in the code. Some code introspects itself to get the name of its class, then lowercases and pluralizes it to become the key in the state object.
The snapshots slice in dev mode looks like this.
That key is derived from the class called
Snapshot
.But when we build for production, that class becomes the single letter
p
.So on zui insiders, the state object looks like.
There is other code that relies on there being a "snapshots" key in the state and that is where the error occurs.
This fix introduces a static, explicit name for the key, instead of the derived one. Looks like we will need to do this each time we introduce a new slice of state in this way.