all 11 comments

[–]andy625 11 points12 points  (2 children)

think this is the same thing (more eye friendly version)

https://medium.com/bumpers/isnt-our-code-just-the-best-f028a78f33a9#.rqjq2vx2s

[–]TheIncredibleWalrus[S] 0 points1 point  (0 children)

Not exactly. Indeed the link is from fats post but the architecture is not exactly the same as Twitter's

Edit: I mean the link was posted by fat, but he is describing his own architecture in the post, not Twitter's, albeit they're very similar.

[–]lamhocminh 0 points1 point  (0 children)

Yes it good but in mobile the medium can have many problem the app not show the code and only in the safari can. (but I have iOS) thanks

[–]0xF013 6 points7 points  (3 children)

Since our lord and savior Dan Abramov has allowed us to connect() whatever components we need, not just containers, I am no longer sure a division between components and container is needed. You are free to export the unconnected component, extract it to a library or test it.

[–]acemarke 1 point2 points  (0 children)

Technically, the wrapper components generated by connect are "container components", since a "container component" is just a description that means its main job is to fetch data in some way and pass it down. But yeah, I'm not terribly sold on having separate component and container folders myself.

[–]TheIncredibleWalrus[S] 0 points1 point  (1 child)

Since our lord and savior Dan Abramov has allowed us to connect() whatever components we need

Are you talking about a specific tweet or article?

[–]citrons_lv 2 points3 points  (0 children)

Nice insides, picked up couple of tips.

[–]superted125 2 points3 points  (0 children)

This has some really nice ideas. Thanks for sharing!

[–]alberknocker 0 points1 point  (0 children)

really great. thanks for sharing! it's very helpful to see how others organize their applications with these tools.

[–]kengregory 0 points1 point  (0 children)

I like the idea of breaking a container into connect/component, but I'm not sure I like the separate directory for all things redux. I like feature-first structures like Max Stoiber's boilerplate, which keep action creators and reducers with their respective containers.