Managing errors for your routes
It does not make much sense to go to a link if the page we go to is not found or is not working. Traditionally, we are presented with an error page when this happens. In an SPA, we are more powerful and we can prevent the user from going there altogether, displaying a little courtesy message stating that the page is not available. This greatly enhances the UX since the user can immediately take another action without the need to go back.
Getting ready
In order to follow along, you should complete the Fetching data before switching route recipe.
This recipe will build up on top of it and I'll assume that you already have all the relevant code in place.
How to do it…
As said, we will edit the resulting code from the Fetching data before switching route recipe to manage errors. Just so you remember, when going to the /aboutme page, we were loading information from the Internet. We want to avoid going to that page in case the information is not available.
For this recipe...
