-
Notifications
You must be signed in to change notification settings - Fork 169
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
Add routing to admin portal #3164
Add routing to admin portal #3164
Conversation
TODOs discussed during sync review:
|
af7eebb
to
3e79412
Compare
Please rebase pull request. |
3e79412
to
e6483d9
Compare
e6483d9
to
0eba3e2
Compare
a9537bd
to
352f355
Compare
The existing functionality using this appears to be non-functional, but its behavior is preserved.
352f355
to
189e827
Compare
- Use FluentUI DetailsList for contents - Always display all properties, even if value is not present - Modify E2E test to check each individual property
189e827
to
8d43f56
Compare
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.
+1 Routing is a hard thing to bring in if not done from the start but this looks like a good step!
<Stack styles={contentStackStylesNormal}> | ||
<Stack horizontal> | ||
<ShimmeredDetailsList |
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.
+1 For bringing in premade React components from fluentui.
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 to me
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 to me thanks!
* Add React Router library * Use React Router for search params The existing functionality using this appears to be non-functional, but its behavior is preserved. * Use cluster resourceID in route for details modal * Use URL routing to handle Cluster Details navigation * Route all admin portal frontend subroutes to index.html * Add handling to portal login redirect to preserve original path * Update E2E tests for new admin portal routing * Replace OverviewComponent with new implementation - Use FluentUI DetailsList for contents - Always display all properties, even if value is not present - Modify E2E test to check each individual property * Build frontend artifacts
Which issue this PR addresses:
Fixes ARO-3500
What this PR does / why we need it:
Changes the URL of the Admin portal based on navigation state:
/overview
).Details for an individual cluster can be routed to directly and linked to.
Test plan for issue:
Is there any documentation that needs to be updated for this PR?
N/A
Additional Notes
<OverviewComponent>
to display cluster properties in a Fluent UI<DetailsList>
, as well as changes the presentation logic to display all known properties whether they are present on the given cluster or not.