Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup Error Boundary to activate upon receiving and error and research how to test #670

Open
dkd2101 opened this issue Nov 19, 2023 · 0 comments
Labels
bug Something isn't working frontend low low priority triaged Has been viewed and assigned priority

Comments

@dkd2101
Copy link
Contributor

dkd2101 commented Nov 19, 2023

  • Right now the Error Boundary component is not being rendered when an error is thrown despite being implemented within the app

  • The error boundary should render the ClientSideError component whenever it is triggered which is currently being passed in the fallback component of the ErrorBoundaryProps

  • Right now whenever a error is thrown in dev, the NextJS overlay is displayed. When tested in frontend version the error is displayed in console but the Error Boundary is not run or displayed.

#653 is the issue that implemented this Error Boundary and created the ClientSideError component.

@dkd2101 dkd2101 added bug Something isn't working low low priority labels Nov 19, 2023
@BrandonLim8890 BrandonLim8890 added frontend triaged Has been viewed and assigned priority labels Dec 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working frontend low low priority triaged Has been viewed and assigned priority
Projects
None yet
Development

No branches or pull requests

2 participants