Internal Server Error Page

[farisashai]

custom 500 page makes it easier to recover to a stable client state by logging out (clearing all cookies)

can design something nicer later on

this page will be hit when serversideprops hits an exception such as

• corrupted cookies
• existing but invalid auth token
• api goes down
• invalid api response

the first 2 cases are easily recoverable by logging out and the last 2 make the portal unusable anyways so they can't be solved by the user

Type of Change

• Bug Fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as
  expected)
• Logistics Change (A change to a README, description, or dev workflow setup like
  linting/formatting)
• Continuous Integration Change (Related to deployment steps or continuous integration
  workflows)
• Other: (Fill In)

Testing

I have tested that my changes fully resolve the linked issue ...

• locally on Desktop.
• on the live deployment preview on Desktop.
• on the live deployment preview on Mobile.
• I have added new Cypress tests that are passing.

Checklist

• I have performed a self-review of my own code.
• I have followed the style guidelines of this project.
• I have documented any new functions in /src/lib/* and commented hard to understand areas
  anywhere else.
• My changes produce no new warnings.

Screenshots

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
membership-portal-ui-v2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 20, 2024 4:43pm

[alexzhang1618]

lgtm, is there a screenshot of the page?

[farisashai]

just go to /500

[alexzhang1618]

[alexzhang1618]

Can we make the link blue so it's clear that it's clickable?