-
Notifications
You must be signed in to change notification settings - Fork 7
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
Feature branch/tet 613 refactor investment project #6465
Feature branch/tet 613 refactor investment project #6465
Conversation
Passing run #50926 ↗︎
Details:
Review all test suite changes for PR #6465 ↗︎ |
src/client/modules/Investments/Projects/Evidence/ProjectEvidence.jsx
Outdated
Show resolved
Hide resolved
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.
The changes you have made all look good to me and are working as expected on my end. In fact, I really like how the pages now load.
However, I did note that when testing if the error messages load with an unknown project ID, clicking on the Admin tab caused an error and the app to crash.
After clicking on the Evidence
tab, the error messages appear as expected:
After clicking on the Admin
tab, the app crashed:
Console output:
error: uncaughtException: Cannot destructure property 'id' of 'res.locals.investment' as it is undefined.
TypeError: Cannot destructure property 'id' of 'res.locals.investment' as it is undefined.
[nodemon] app crashed - waiting for file changes before starting...
This can also be replicated on the staging environment with a 504 error, so most likely a pre-existing issue.
I'd be happy to discuss further, but thought we might want to investigate some more before publishing this change as it could potentially increase the chance of users accidentally experiencing the issue.
e483fa2
to
863c26b
Compare
…ce, create new layout and layout header for investments
… project resource
…crumbs for Interactions and Evaluation
…ered before the resource
…on list component
863c26b
to
c1258fb
Compare
e0cae66
to
fee5e75
Compare
…-RefactorInvestmentProject generated from commit 5696a8d
Description of change
Refactor project investment pages so that the layout is rendered before the resource is loaded. Create new layouts for the investment pages to use so that inline resources can be rendered for better user experience if there are errors.
Test instructions
These steps use 'Super Awesome Project' as an example investment project but you can use any investment project to test the changes.
To carry out these steps, run the dev environment locally.
From the Data Hub homepage, navigate to the Investments page
Select an Investment Project to load the Project details page e.g. Super Awesome Project
You should see the page layout load before the page resources i.e. you should be able to see the page header and left hand navigation whilst the Investment information is loaded (see screen shots below for an example). Loading wheels should appear inline.
To test that the page displays error messages inline when an investment cannot be loaded, update the ProjectId to an unrecognisable string
e.g.
Screenshots
Before
Appearance of Project Team page with no errors:
After
Appearance of Project Team page with no errors:
Before
Appearance of Project Team page with errors:
After
Appearance of Project Team page with errors:
Checklist