Forward redux events to remote stores #247
Open
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
…es to support side-effects there.
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.
Hey folks, thanks for a great package! I ran into the same issue as a couple other people where I wasn't getting actions to trigger my side-effects on my remote stores. I added a redux middleware to the background store in
wrapStorethat drops every action into the message bus for the remote stores and re-dispatches them on the remote so they can get picked up by side-effects.NB: I didn't think carefully about the ordering of messages here because it doesn't matter for my use case, but would probably be a good idea if you've got the time to think about when the actions and state patches arrive at the remote ;)