-
Notifications
You must be signed in to change notification settings - Fork 646
Add Figma Code connect PageHeader #5757
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
|
|
👋 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! |
|
Uh oh! @lukasoppermann, 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.
|
size-limit report 📦
|
| contextArea: figma.children('_PageHeader.ContextArea'), | ||
| }, | ||
| example: ({description, hasBorder, titleArea, navigation, contextArea}) => ( | ||
| <PageHeader hasBorder={hasBorder}> |
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.
It looks like TypeScript is complaining about hasBorder here, what is the corresponding prop for this in React? I couldn't seem to find a reference for borders in PageHeader 🤔
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.
This is the corresponding prop, I just wait for it to get merged. 😄
Adds Figma Code connect file for PageHeader
This needs #5741 to be merged as we otherwise get a typescript error.
Changelog
New
Changed
Removed
Rollout strategy
→ No change to react, the standard process for those changes is to not increase the version.
Testing & Reviewing
Merge checklist