Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #96
I've used a small wrapper (
ky
) aroundfetch
to unify HTTP response error handling. Whenever we receive a non-200 HTTP response, it throws anHTTPError
that is caught by the error boundary around the routes. We can still display the 404 page by throwing aNotFoundPageError
, for example, when requesting a non-existent submodule within an existing module's data.I've also moved all routes under a route layout to use a single error boundary – I recommend disabling whitespace changes on the diff view.