chore: move state management to context #73
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.
Building further upon #58, and #68, I've moved all shared state management to the context. I believe this greatly simplifies state management.
The context provider is placed now a level deeper, directly in
Playground, instead of wrapping the router as well. This enables us to provide theinitialValuesdirectly to the context.To implement state management in the context, I've implemented a state reducer. All components that use the state, now import a
stateobject and adispatchfunction, and that's it.No more
editor refsor directly setting editor values from within other components. And the parser is now called directly upon state mutation, instead of later via useEffect.In the scope of the "where to save state" discussion that was being held in #58, I've added an
onChangehandler to the context. This onChange handler can be used to sync state to storage locations. As can be seen inPlaygroundandEmbedded.