-
Notifications
You must be signed in to change notification settings - Fork 144
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
ROX-27391: Update Workload CVE page title with dynamic string #13616
base: master
Are you sure you want to change the base?
Conversation
Skipping CI for Draft Pull Request. |
Images are ready for the commit at bb4b2b4. To use with deploy scripts, first |
@@ -161,11 +163,11 @@ function NamespaceViewPage() { | |||
|
|||
return ( | |||
<> | |||
<PageTitle title="Workload CVEs - Namespace view" /> | |||
<PageTitle title={`${pageTitle} - Namespace view`} /> |
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.
Aha, we will need to double down on separation of subroute after information architecture is clearer?
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.
Likely yes. From what I can tell, the "Platform Components" filter does work with the queries on the namespace route, so separate routes for both user and platform level workloads should be supported. I'll have to confirm with the team that this is what we want.
df34593
to
aefbcb7
Compare
e62ee1b
to
bb4b2b4
Compare
Description
Instead of a hard coded "Workload CVEs", reads the page title and breadcrumb navigation link string from the page context.
User-facing documentation
Testing and quality
Automated testing
How I validated my change
Navigate through Workload CVE pages and ensure the page title and breadcrumb link continue to read "Workload CVEs".