-
Notifications
You must be signed in to change notification settings - Fork 9
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
BHBC-2274: Router technical debt #983
Conversation
Openshift URLs for the PR Deployment: |
Codecov Report
@@ Coverage Diff @@
## dev #983 +/- ##
===========================================
- Coverage 80.85% 68.11% -12.75%
===========================================
Files 177 378 +201
Lines 7027 11722 +4695
Branches 1225 1987 +762
===========================================
+ Hits 5682 7984 +2302
- Misses 1065 3290 +2225
- Partials 280 448 +168
... and 189 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Openshift URLs for the PR Deployment: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📸
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐤
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Overview
Fixes some minor annoyances + addresses some technical debt surrounding the app router
Links to Jira tickets
Description of relevant changes
Replaces normal anchor links with React Router links
Removes unneccessary routes:
surveys/:survey_id/attachments
surveys/:survey_id/observations
surveys/:survey_id/results
Removes
<Layout>
components that are already wrappedFixes an issue with the Forbidden page, wherein users cannot navigate away from the forbidden page if the initial request to fetch the user's userdata fails. This often occurs during development when the app refreshes while the API is momentarily re-compiling.
Testing Procedures
api/src/app.ts
in your IDE and saving the file, triggering a rebuild of the API. If this is successful, you should land on the Forbidden page in SIMS.