Reactify route-based errors #20543
Labels
enhancement
New value added to drive a business result
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
We currently have three errors which are surfaced via individual Angular routes:
We'll need to convert this code to React. As part of this process, we should consider removing the need for specialized routes altogether since the UX of allowing a user to navigate to an error page when there's no error doesn't make sense. It also seems unhelpful to navigate out of the context which caused the error. As an alternative we could display a large modal. We should also ask our copywriting team to take a look over the copy while we're at it.
The text was updated successfully, but these errors were encountered: