feat(dashboard): Wrap each route in an ErrorBoundary

[kasperkristensen]

What

• Updates the copy of the different error types
• Wraps each route (+ custom routes) in an ErrorBoundary to preserve app layout on error (sidebar and topbar)

Note
If the user goes to a route that does not exist at all, e.g. /some-weird-url, then we have no way of knowing if the user is inside of a context where we can render the sidebar and topbar (as they require the user to be authenticated). So in this case we still show an ErrorBoundary where the two aren't included (see second picture), and include a button that takes the user to "/", which depending on whether the user is logged in will take them to "/login" or "/orders".

Resolves CC-248

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
api-reference	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Aug 20, 2024 1:02pm
medusa-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 20, 2024 1:02pm

5 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
api-reference-v2	⬜️ Ignored (Inspect)	Visit Preview		Aug 20, 2024 1:02pm
docs-ui	⬜️ Ignored (Inspect)	Visit Preview		Aug 20, 2024 1:02pm
docs-v2	⬜️ Ignored (Inspect)	Visit Preview		Aug 20, 2024 1:02pm
medusa-docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 20, 2024 1:02pm
resources-docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 20, 2024 1:02pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 398e1db

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[olivermrbl]

So in this case we still show an ErrorBoundary where the two aren't included (see second picture), and include a button that takes the user to "/", which depending on whether the user is logged in will take them to "/login" or "/orders".

Nice, sounds like a good solution.