Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alert page 404 #4180

Merged
merged 2 commits into from
Oct 5, 2019
Merged

Alert page 404 #4180

merged 2 commits into from
Oct 5, 2019

Conversation

ranbena
Copy link
Contributor

@ranbena ranbena commented Sep 24, 2019

  • Feature

Description

Handle Alert 404.

Before:

Screen Shot 2019-09-24 at 10 27 34

After:

Screen Shot 2019-09-24 at 10 27 23

Copy link
Member

@arikfr arikfr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We actually have standard behavior for 404s. You can trigger it either by returning the logic of loading the alert to the route's resolve or by throwing the relevant exception. I don't remember the details, but maybe @kravets-levko remembers / has relevant example?

@ranbena
Copy link
Contributor Author

ranbena commented Sep 24, 2019

Updated 👍

Screen Shot 2019-09-24 at 11 04 52

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants