Skip to content

Make a helpful 404 page

Brendan Berkley requested to merge spruce-up-404 into master

I wanted to do something beyond "404 page not found" so I threw this together. Dunno if the container and stuff is overkill, but I like the idea of 1) having the bad route right in your face (particularly if you're in a browser that obscures the URL) and 2) having links that show based on whether or not you're logged in.

Eventually I'd love to get the robot in here!

Are there any technical considerations here? I know this isn't a true 404 in the sense that it's really just the default route inside the Angular app. So I don't know. Do we need to simulate any other error codes in a full-page manner like this?

Also, my routerLinks are going to root level (/account instead of ./account) - will that ever be a problem? Will anyone ever do example.com/passit as a URL? But if my bad URL is /account/impoooort, ./account takes me to /account/account.

Merge request reports