wcifto
Handling 404 within existing catch-all route
Great thank you. I was also thinking a combination of both a Show and ErrorBoundary as well.
For example 2 scenarios:
- CMS response is ok, just no data/no route exists -->
<Show> renders a NotFound component
- CMS response throws error/4xx/5xx, bigger problem at hand --> <ErrorBoundary> displays some more error-specific information than NotFound5 replies