-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple stores #9
Comments
@eiktyrner Thanks for the suggestion. Right now I'm using a single store object for my mobx apps but you're right, this should be supported too. Also see the discussion in #12 👍 |
@kitze Just right after having installed this I found the same problem as @eiktyrner. Thanks for sharing this by the way 👍 👍 |
For now I'm doing this and always injecting specific stores instead of the
|
I just ran into this as well. The generic MobX error made it a bit difficult to track down. Any plans to support a custom store name instead of requiring |
Combining multiple stores is recommended as best practice if you plan to have multiple stores. Also, +1 for support to have a custom name instead of |
Is it possible to use this package with multiple stores? Or do you need a "root" store like in your examples?
I'd rather not have just a single store available for injecting like your example
export default observer(['store'], Gallery);
My current setup with ReactRouter is along these lines (from memory so syntax might be off..)
I couldn't get the startRouter to work with this type of setup. Any input?
The text was updated successfully, but these errors were encountered: