-
Notifications
You must be signed in to change notification settings - Fork 622
Add prop to PageHeader to allow a bottom border #5741
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
🦋 Changeset detectedLatest commit: 18f09dd The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Uh oh! @mperrotti, at least one image you shared is missing helpful alt text. Check your pull request body to fix the following violations:
Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image. Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.
|
👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks! |
size-limit report 📦
|
@@ -754,6 +762,7 @@ const Navigation: React.FC<React.PropsWithChildren<NavigationProps>> = ({ | |||
aria-label={as === 'nav' ? ariaLabel : undefined} | |||
aria-labelledby={as === 'nav' ? ariaLabelledBy : undefined} | |||
className={clsx(enabled && classes.Navigation, className)} | |||
data-component="PH_Navigation" |
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.
data-component="PH_Navigation" | |
data-component="PageHeader.Navigation" |
One suggestion that could make it more clear what the component is when coming back to this later
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.
PH_{Subcomponent}
is the naming pattern we use for the other subcomponents. Do you still think we should change it?
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.
I think we're kind of trying to move away from data-component
actually.. what about just giving it a classname instead?
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.
I agree, PageHeader.Navigation
is more clear, but to keep it consistent I think PH_{Subcomponent}
is fine too! Would be curious about the className route too 👀 Maybe we'll want to revisit in a different PR to adjust the existing data-* attributes.
@mperrotti somehow I can't add this comment to the code, but we need this: |
Co-authored-by: Josh Black <[email protected]>
@lukasoppermann - I thought I handled those cases already, but I must have broke something. I'll take another look. |
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.
Snapshots look good here & in storybook
I'm not sure if the naming pattern discussion is resolved, but story + snapshots lgtm 👍
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!
Relates to https://github.com/github/primer/issues/2837
Changelog
New
hasBorder
prop onPageHeader
Changed
Removed
Rollout strategy
Testing & Reviewing
Merge checklist