The Errror 500 component has a button on it called "back to form" which redirects to "/". It's also nested in an anchor tag. This is invalid html, it shouldn't be a button, the anchor tag is sufficient. However, we're using react router, so we shouldn't be using native anchor tags, we should use ReactRouter's or components.
And in general this feels like bad UX. 500 is a server error happening because an API call we made went wrong server-side. We should handle that in the place that is calling the API and show an appropriate message to the user.
So for example, if the registration form failed to save, we should stay on the page and tell the user to try again. But if loading the attendees list on the admin page, we'd want to show a different error message.
I think in general it's probably better to remove this component completely.
The Errror 500 component has a button on it called "back to form" which redirects to "/". It's also nested in an anchor tag. This is invalid html, it shouldn't be a button, the anchor tag is sufficient. However, we're using react router, so we shouldn't be using native anchor tags, we should use ReactRouter's or components.
And in general this feels like bad UX. 500 is a server error happening because an API call we made went wrong server-side. We should handle that in the place that is calling the API and show an appropriate message to the user.
So for example, if the registration form failed to save, we should stay on the page and tell the user to try again. But if loading the attendees list on the admin page, we'd want to show a different error message.
I think in general it's probably better to remove this component completely.