Skip to content
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

Get closer to Elm architecture #136

Closed
gaearon opened this issue Oct 3, 2015 · 3 comments
Closed

Get closer to Elm architecture #136

gaearon opened this issue Oct 3, 2015 · 3 comments

Comments

@gaearon
Copy link
Contributor

gaearon commented Oct 3, 2015

It seems that with the current Provider/connect and Smart/Dumb component distinction, some things from Elm Architecture become harder than they should be. In particular, nesting actions, and examples like “generic list” (reduxjs/redux#822).

It is possible that we need to tweak the API and conventions to better represent Elm Architecture and thus benefit from it. How exactly, I'm not sure yet.

@aflatter
Copy link

@gaearon Just out of interest: Was there any conclusion on this topic?

@gaearon
Copy link
Contributor Author

gaearon commented Oct 28, 2015

I don't think it makes sense for us to do this. Neither Redux Middleware, nor React play well with Elm-like nesting. If somebody wishes to write their app in a completely Elm Arch-like way, they are free to do so: they just wouldn't use middleware, and would compose updater functions at the component level.

@gaearon
Copy link
Contributor Author

gaearon commented Mar 18, 2016

Relevant new discussion: reduxjs/redux#1528

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants