add data-component attributes for Avatar, AvatarStack, Banner, & BaseStyles#7734
add data-component attributes for Avatar, AvatarStack, Banner, & BaseStyles#7734llastflowers wants to merge 15 commits intomainfrom
Conversation
🦋 Changeset detectedLatest commit: 0d4323c 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 |
|
| const root = container.querySelector('[data-component="AvatarStack"]') | ||
| expect(root).toHaveAttribute('data-align-right', '') |
| <Button | ||
| data-component="Banner.SecondaryAction" | ||
| ref={forwardedRef} | ||
| className={clsx('BannerPrimaryAction', className)} | ||
| variant="invisible" | ||
| {...rest} | ||
| > |
There was a problem hiding this comment.
not relevant to this PR but why is this class=BannerPrimaryAction? 😳
There was a problem hiding this comment.
Good point! I looked into it and it seems like it's been this way since the inception of Banner.tsx 😅 Probably just a copy/paste error by the looks of it! But another thing aside from that—it seems like this might actually be a legacy thing that isn't even in use?? Unless I'm just not understanding how its used 🤔 I'd be curious to know what you think!
There was a problem hiding this comment.
my guess would be if you want a stable class to select 'cause after ours are computed they get a random value added to them, but this definitely feels like an error 🤔 , either way let's keep it outside the scope of this PR
francinelucca
left a comment
There was a problem hiding this comment.
I think after #7734 (comment) we're good to go here 👍🏽
Add data-component attributes for Avatar, AvatarStack, Banner, and BaseStyles.
|
👋 Hi from github/github-ui! Your integration PR is ready: https://github.com/github/github-ui/pull/18946 |
|
Integration test results from github/github-ui:
CI check runs linting, type checking, and unit tests. Check the workflow logs for specific failures. VRT check ensures that when visual differences are detected, the PR cannot proceed until someone acknowledges the changes by adding the "visual difference acknowledged" label. Need help? If you believe this failure is unrelated to your changes, please reach out to the Primer team for assistance. |
Relates to https://github.com/github/primer/issues/6497
Changelog
New
Add data-component attributes and associated for Avatar, AvatarStack, Banner, & BaseStyles
Rollout strategy
Testing & Reviewing
Merge checklist