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.
Refactor main.js into namespaced models; add tests for effects/reducers
See original GitHub issueAs per discussion in #190, we should be able to add unit tests for effects and reducers. Before we can do this, I think it would make sense to break apart the monolithic model in main.js. I think we can do this simply by creating 2 namespaced models, issues and address (to avoid confusion with the special location namespace choo provides for interacting with the window.location object), and then just keep a barebones set of initialization logic in the top level model.
Once that is done, we can start filling in unit tests for our reducers and effects.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (6 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
Can we hold off on this until we get some more clarity on #260? I don’t want to waste anyone’s time here without knowing the timeline on getting away from choo v4.
This is resolved now that we’re moving to react, no more monolithic main.js