Skip to content
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

Remove option large from ButtonGroup story #3802

Merged
merged 2 commits into from
Oct 13, 2023

Conversation

lukasoppermann
Copy link
Contributor

According to the docs large is not a valid option.

Changed

Removed large option from storybook property

Rollout strategy

  • Patch release
  • Minor release
  • Major release; if selected, include a written rollout or migration plan

Merge checklist

  • Added/updated tests
  • Added/updated documentation
  • Added/updated previews (Storybook)
  • Changes are SSR compatible
  • Tested in Chrome
  • Tested in Firefox
  • Tested in Safari
  • Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

According to the docs `large` is not a valid option.
@lukasoppermann lukasoppermann requested review from a team and langermank October 10, 2023 11:03
@changeset-bot
Copy link

changeset-bot bot commented Oct 10, 2023

⚠️ No Changeset found

Latest commit: b9c8f4c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Contributor

github-actions bot commented Oct 10, 2023

size-limit report 📦

Path Size
dist/browser.esm.js 104.74 KB (0%)
dist/browser.umd.js 105.32 KB (0%)

@lukasoppermann lukasoppermann added the skip changeset This change does not need a changelog label Oct 10, 2023
@lukasoppermann lukasoppermann temporarily deployed to github-pages October 10, 2023 11:09 — with GitHub Actions Inactive
@github-actions github-actions bot temporarily deployed to storybook-preview-3802 October 10, 2023 11:10 Inactive
@joshblack
Copy link
Member

Question for the team, is there anything we can do at a type-level or at runtime to catch this kind of issue? 🤔 cc @primer/react-reviewers

@lukasoppermann
Copy link
Contributor Author

Question for the team, is there anything we can do at a type-level or at runtime to catch this kind of issue? 🤔 cc https://github.com/orgs/primer/teams/react-reviewers

Couldn't we technically add a size property to buttonGroup instead of just passing the props on?

@joshblack
Copy link
Member

@lukasoppermann I think that could definitely be an option 💯 Right now it seems like folks just pass the size option to Button directly. This approach would need some plumbing to set things up (e.g. Button reads from context for it) but is super do-able.

Another pattern might be to iterate through children and provide the size prop through cloneElement but this path feels discouraged these days 😞 (context)

@lukasoppermann lukasoppermann added this pull request to the merge queue Oct 13, 2023
Merged via the queue into main with commit caf7c50 Oct 13, 2023
28 checks passed
@lukasoppermann lukasoppermann deleted the lukasoppermann-fix-buttonGroup-props branch October 13, 2023 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip changeset This change does not need a changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants