-
Notifications
You must be signed in to change notification settings - Fork 154
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
Modular api to satisfy #68 #71
Conversation
Hm. I didn't realize it was going to want to merge five pointless commits. I can resubmit with just the latest, if that's a problem. |
@randallsquared Thanks so much, this is awesome! I'm out of town soon but will take a closer look ASAP. Feel free to squash and force push over the branch. |
a0f727e
to
316e46e
Compare
Fixed up commits. |
Add new method on Dispatcher: addStore to support Flux#addStore Add tests for new api functionality New: Remove misleading comments in favor of descriptive variable naming New: Edit wording of error messages for clarity
316e46e
to
9904d77
Compare
Fixed up some strings and comments which were misleading. |
This looks great, @randallsquared, thanks again. #51 and #39 deal with the store API, so I don't think there's an issue here. |
Oh, okay. :) |
No problem! |
This implements a superset of the API mentioned in #68 with addActions/addStores supporting the current object format (and used by the Flux constructor), and addAction/addStore supporting the one-at-a-time notion.
Flux#addStore takes a name and a store, and adds the store to Flux.
Flux#addAction takes either an array of namespaces and an action function, or any number of namespaces as strings, and then an action function.
bindActions was changed to throw when encountering a collision.
I didn't check in any documentation, but I can do so if you'd prefer that to writing it yourself.