jcoreio / jcoreio/redux-utils-immutable
improve dev experience
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
debugging issues with combineReducers etc. can be tricky because it's not immediately obvious where the problematic reducer was created. I need to figure out the best way to ease debugging in this case. One idea is to store a stack trace when combineReducers etc. is called (as long as process.env.NODE_ENV !== 'production', and if applying the reducer throws an error, include the creation stack trace in that error somehow.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the combineReducers call and the point where the composed reducer applies its reducers and throws. Compare development behavior with NODE_ENV set to production, then define how a creation stack should be retained and surfaced in the error; the issue is done when reducer origin is easier to identify without adding production overhead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100