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

Use FallbackComponent when route throws an exception while rendering #5755

Merged
merged 5 commits into from
May 8, 2023

Conversation

HelNershingThapa
Copy link
Contributor

Resolves #5754

- Specify our custom FallbackComponent as the ErrorBoundary component for root route path
Reverting the removal of Suspense. I thought the fallbackElement would suffice the use of Suspense but it didn't. Bringing that back.
frontend/src/App.js Outdated Show resolved Hide resolved
--------------------------------------------------

Previously, there were two instances of the <RouterProvider> component being rendered vertically in the code, causing the app to appear twice on the page. This was an oversight that I have corrected by removing one of the instances.
@sonarcloud
Copy link

sonarcloud bot commented May 8, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@Aadesh-Baral Aadesh-Baral merged commit 4786c63 into develop May 8, 2023
5 checks passed
@Aadesh-Baral Aadesh-Baral deleted the enhancement/5754-error-boundary-root-route branch May 8, 2023 05:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Display our custom FallbackComponent when exceptions are thrown
2 participants