You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: