-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
fix(ButtonGroup): add and improve types and add tests #3220
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
fix(ButtonGroup): add and improve types and add tests #3220
Conversation
|
✔️ Deploy Preview for react-native-elements canceled. 🔨 Explore the source changes: f9d6e0b 🔍 Inspect the deploy log: https://app.netlify.com/sites/react-native-elements/deploys/61e1363a1a7d30000773e4d8 |
|
Can you merge |
Codecov Report
@@ Coverage Diff @@
## next #3220 +/- ##
==========================================
+ Coverage 79.13% 79.24% +0.11%
==========================================
Files 87 87
Lines 1807 1807
Branches 793 792 -1
==========================================
+ Hits 1430 1432 +2
+ Misses 370 369 -1
+ Partials 7 6 -1
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
Co-authored-by: Arpit Bhalla <55053424+arpitBhalla@users.noreply.github.com>
Co-authored-by: Arpit Bhalla <55053424+arpitBhalla@users.noreply.github.com>
What kind of change does this PR introduce?
Improve Types(ButtonGroup)
Did you add tests for your changes?
yes.
If relevant, did you update the documentation?
it is already exists.
Summary
{element: componentName}forbuttonsprops, but TypeScript doesn't have that type, thus I added a type.buttonsis entered in an array other than a string.Does this PR introduce a breaking change?
no.
Other information
I was thinking the #3196 problem could be solved with
{element: componentName}.However, improving #3196 required modification of the parent component. This PR does not directly resolve it.