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.
Pages stuck in "loading" mode when an error is thrown
See original GitHub issueWhen we use a loading flag in a reducer and the API layer throws an error (e.g. 400 or 404), then the redux state keeps loading set to true, which results in a page stuck in “loading” mode sent by the server.
For instance, here is a search result that throws a 400: https://addons.allizom.org/en-US/firefox/search/?platform=pouet&q=ad&type=extension. We do not get any error displayed and the page does not look nice. In #3268, I implemented a similar mechanism that should render a NotFound component when a 404 error is caught. Yet this does not work either.
Note: This does not seem to be the case when SSR is disabled.
Issue Analytics
- State:
- Created 6 years ago
- Comments:28 (24 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
Nope, I’m not; I’ve unassigned myself as I’m working on a few UI polishes before the tag.
I’ve logged https://github.com/mozilla/addons-frontend/issues/3887 We can mark this one verified.