-
Notifications
You must be signed in to change notification settings - Fork 538
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
feat(VisuallyHidden): Convert VisuallyHidden to CSS module behind feature flag #5193
Conversation
🦋 Changeset detectedLatest commit: 04dd885 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 |
👋 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 📦
|
👋 Hi from github/github! Your integration PR is ready: https://github.com/github/github/pull/349259 |
🟢 golden-jobs completed with status |
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 great! Just left a comment in case it's helpful info. I think you're totally good to go though since integration checks passed 🔥
@@ -12,17 +19,34 @@ import sx from '../sx' | |||
* | |||
* @see https://www.scottohara.me/blog/2023/03/21/visually-hidden-hack.html | |||
*/ | |||
export const VisuallyHidden = styled.span<SxProp>` |
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.
Just wanted to share in case it was helpful (and feel free to ignore me if this is obvious 😂), when migrating styled components that are exported two helpful things I've found to double-check check are the as
prop and ref
support.
When we update these kinds of components these don't come along and they may be used downstream. It's hard to tell if these are breaking changes or not so I think we've been evaluating it by seeing if they are used this way in dotcom when updating.
Thankfully the integration tests tend to do a good job of double-checking this, also feel free to use Primer Query (e.g. this link, if you need to login then you'll have to click the link again since query params aren't persisted 😅)
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.
Thank you for the reminder. I'll definitely add this to my routine on components moving forward!
Related To: https://github.com/github/primer/issues/4368
Closes: https://github.com/github/primer/issues/4368
Changelog
Changed
Convert VisuallyHidden component to css module behind feature flag
Rollout strategy
Testing & Reviewing