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

react - redux architecture examples #9

Open
alexnm opened this issue Dec 3, 2016 · 8 comments
Open

react - redux architecture examples #9

alexnm opened this issue Dec 3, 2016 · 8 comments

Comments

@alexnm
Copy link

alexnm commented Dec 3, 2016

Hello clujsers, I'm interested in learning new / different approaches for architecting larger applications with React and Redux and I thought this might be a good place to share some codebase examples. I'm currently working on one and I'll try to have it on github in a few days.

Who wants to join the conversion? :)

@andrei-cacio
Copy link
Member

hi @alexnm, I really like the idea. I started experimenting with some new approaches on my own but I don't have something solid... yet at least. However, I would really like to see your approach 👍

@danburzo
Copy link

danburzo commented Dec 5, 2016

Subscribing to this thread 👍

@tudorgergely
Copy link
Contributor

Maybe we can create a repository here and people can come with different approaches as pull requests. This way we can see all of them in one place :)

@alexnm
Copy link
Author

alexnm commented Dec 6, 2016

It would be great just to discuss first various alternatives and then maybe we can come up with a combined approach

@alexnm
Copy link
Author

alexnm commented Dec 10, 2016

This is my theoretical take on the redux part: https://github.com/alexnm/re-ducks. Will follow-up with a boilerplate / start thingy asap.

@danburzo
Copy link

Hi Alex, it looks very good. I'll give it a closer read.

What I'd be interested to hear from this conversation is how you're shaping your actions and your state, and how that impacts the reducers.

Case in point: we're currently using FSA actions, but there seems to be a lot of boilerplate in the reducer around the status of the async call (before/in progress / success / failure), and I'm curios how everyone is dealing with that.

As for the state shape, we're splitting each sub-state in ui and data components, with the former keeping transient state (such as list vs. grid view, search term, filter states), and data for the things that come from permanent storage. Any other approaches around this?

@alexnm
Copy link
Author

alexnm commented Jan 17, 2017

Ok, I managed to put this on github, but it's still work in progress: https://github.com/FortechRomania/react-redux-complete-example

Can anyone share other links or examples they have?

@danburzo
Copy link

Awesome, thanks @alexnm, I'm taking a look. I'm also planning on sharing some architecture guidelines after we sort out some things — right now it's a bit in flux :)

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

No branches or pull requests

4 participants