-
Notifications
You must be signed in to change notification settings - Fork 0
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
using store module with store object reference instead of string key #1
Comments
@mha15 The purpose of |
for example create
use
|
Ah, I see. You example API can be recreate easely in top of the current API: Ex:
I am not sure if these types of cases that are more specific should be added to the module. Or just point them out as a pattern in the Doc Actually the |
Or even more simple with:
It is quite likely that you will use this API in the next version, Thanks for suggesting it. |
Hey @mha15 I add your suggested changes to Store API |
I had like store functions very much but I don't want to name my stores and worrying about unique key for them
I think that it might be a good idea that
createStore
can return a store object which have.get
method and module can have another function foruseStore
which will received store as paramsI think that this type of store might not be compatible with already version of it so you can find another name for it
Thanks
The text was updated successfully, but these errors were encountered: