Show Redux Store Differences Triggered by Actions #1531
Conversation
This file contains 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
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.
Please verify the following:
yarn build-and-test:localpassesREADME.md(or relevant documentation) has been updated with your changesDescribe your PR
This change allows developers to see what has been modified in the store after an action is dispatched.
It is particularly useful when an action updates multiple modules. When an action is called in Redux, the current store is compared with the new store, and the differences are sent to Reactotron to be displayed in the timeline.
To determine these differences, the microdiff package was used and added as a dependency to reactotron-redux.
I am not entirely familiar with your build process, but I assume that the microdiff package will be installed automatically via npm/yarn when developers upgrade the Reactotron plugin in their projects.
I'm open to feedback and suggestions for further improvements to this implementation. Please feel free to reach out if you have any questions or if there are areas you'd like me to refine.
closes #496