Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
3.0.0: Questions about the structure of the app
See original GitHub issueAfter getting to know more about the boilerplate I was wondering about a few things:
Where should reducers & actions go which are not connected to any container?
I know this calls for an opinionated answer but it would be interesting to know how you would solve this. Is there maybe a reason why separate actions and reducers are not implemented in the example (except for the global state)?
Where would separate reducers be registered?
Independent from where I keep the code for them, the most reasonable location I found to register any separate reducers with the store is the function createReducer in app/reducers.js. Is that correct?
How about generators for these?
The generators are a great. Would you support generators for reducers and actions as well? I would happily try out creating these as PRs.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
There shouldn’t be any reducers/actions that aren’t associated with any container, if they’re global add them to the uppermost
App! (more info)I’d be interested to hear what sort of actions and reducers that you cannot put anywhere.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.