-
Notifications
You must be signed in to change notification settings - Fork 668
OCPBUGS-54670: Use PF component group for PageHeading #14965
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
Conversation
|
@logonoff: This pull request references CONSOLE-4492 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/unhold |
|
qe review: |
|
@logonoff: This pull request references CONSOLE-4492 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@logonoff: This pull request references CONSOLE-4492 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
code review: /label px-approved |
f88c3cb to
15036b9
Compare
frontend/packages/console-shared/src/components/heading/PageHeading.scss
Outdated
Show resolved
Hide resolved
- adopt `BasePageHeading` when possible (as many pages don't use the extra functionality provided by the `connect`) - Rename `PageHeading` to `ConnectedPageHeading` - Rename `BasePageHeading` to `PageHeading` - move `PageHeading`, `Breadcrumbs` to console/shared - update cypress test to reflect changes
rhamilto
left a comment
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.
/lgtm
Let's see if we can't get this in before branching and address any issues in follow-ons.
| * is not the primary page header to avoid having multiple favourites buttons. | ||
| */ | ||
| hideFavoriteButton?: boolean; | ||
| /** The heading title. If no title is set, only the `children`, `badge`, and `helpAlert` props will be rendered */ |
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.
Not new, but very confusing since title is required. Maybe this should read If title=''...?
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 funny thing though is that we set title={undefined} all the time in our codebase. See the ListPage/FireMan components, where if showTitle is set to false, then it explicitly passes undefined to the title. It appears this has been the behaviour since at least 2017.
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.
Even weirder.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: logonoff, rhamilto The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
/label plugin-api-approved |
|
/retest-required |
|
/retest |
|
Overriding the CI job due to flakiness /override ci/prow/e2e-gcp-console |
|
@jhadvig: Overrode contexts on behalf of jhadvig: ci/prow/e2e-gcp-console DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/label docs-approved |
|
@logonoff: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
@logonoff: Jira Issue OCPBUGS-54670: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-54670 has been moved to the MODIFIED state. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Fix included in accepted release 4.19.0-0.nightly-2025-04-29-095709 |



https://issues.redhat.com//browse/CONSOLE-4492
https://issues.redhat.com/browse/OCPBUGS-54670
follow up on #14875
adopts PF PageHeader for console's main heading component.
no major UI changes should appear in this PR (e.g., create buttons appearing in a separate row as the title), except for two: operator details now have a line between the operator icon and the operator name. badges are also now placed next to the title.
fixes small a11y issue where heading actions were inside of the
h1element when it shouldn't be