Temporary fix to resolve RTK freezing reducer states #2818
Merged
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
As of dcd2c69, the playground code evaluation seems to have been broken and unusable. This is caused by the fact that Redux Toolkit uses
immer
as their state manager. By design ofimmer
, it will auto freeze states causing mutations to fail, even in production.Thus, as we are still in the progress in migrating to RTK, and that various current sagas and actions still depend on these state mutations to work correctly (i.e. code evaluation), it will be good to explicitly disable auto-freezing of the state until the reducer/actions depending on state mutations get refactored.
Type of change
How to test
Ensure that playground code evaluates as normal, and that modules work as intended.
Checklist