Skip to content
Discussion options

You must be logged in to vote

Hey @ibrahimkteish! While it is functionally OK to do so, I wouldn't do it that way personally.

Your reducer's domain is quite large, and this is probably a sign that you can extract some functionalities into smaller reducers. This should also probably help the compiler. Each smaller domain can still have nested _internal, view, and delegate actions if you want, and I'm not saying that you should try to split your domain along these technical boundaries, but rather according to some coherent functionalities (which is something you can only do on a case by case basis).

This should probably help make your code easier to read, compile and test.

Furthermore, if I would adopt this kind of nest…

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@tgrapperon
Comment options

@ibrahimkteish
Comment options

Answer selected by ibrahimkteish
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants