-
Notifications
You must be signed in to change notification settings - Fork 65
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
Add documentation #95
Comments
Great idea, please do, thanks! |
@adam-26 PR is still very welcome. Happy New Year :) |
I'm on vacation :) I'll submit the PR once I'm back in the office.
… Den 7. jan. 2017 kl. 02.11 skrev Vitaly Aminev ***@***.***>:
@adam-26 PR is still very welcome. Happy New Year :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Almost similar to @adam-26 situation, i also have my components setup exactly like this:
But in my router setup, things look like this:
And the thing is the promise never get fired (state-props mapping works fine). If I strip-off the Wrapper everything works perfect - so what is the correct way or workaround to deal with the Promise action in this situation? Note that I dont really want to touch the Wrapper nor the Route setup. |
Hi,
As a reference for others, I think it would be helpful to add the following example to the readme.
This approach allows you to isolate all redux related behaviors to a container, without the need to pollute the component code.
IMHO, i think this is a cleaner approach then using the decorator pattern. Helpful if you want to use packaged components without access to the component source.
Want me to submit a PR?
Adam.
The text was updated successfully, but these errors were encountered: