-
Notifications
You must be signed in to change notification settings - Fork 646
add missing className props and update behavesAsComponent test check #5810
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: 368ed02 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 📦
|
siddharthkp
left a comment
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! ❤️
Only feedback I have is on the changeset, approving in advance!
Co-authored-by: Siddharth Kshetrapal <[email protected]>
Changelog
New
Changed
I noticed that
ActionList.Groupwas missing className so I decided to add it. I also added a test forActionListsub-components to ensure they all supportclassName. Then I realized we could updatebehavesAsComponentto do the check wherever it is being used. While doing so, it causing a few places that were missing displayName and className, which I also updatedclassNameprop to components missing themdisplayNameto components missing themActionListsub-componentsbehavesAsComponentto test for classNameskipClassNameto component checks that require wrapper to render or do not support itRemoved
Rollout strategy
Testing & Reviewing
Merge checklist