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(number-input): uses props of wrapping form-control #2217
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/chakra-ui/chakra-ui/qerdl788m |
anything i can do to get this merged ? |
@silltho sorry we've been quite busy, I personally haven't taken a look but we'll get to it shortly :) |
Ok it's now been open for over 2 weeks. I know you guys are having a lot of work but still that's not developer friendly. A lot of other PRs being merged during this time and this is a really small one. However I keep this PR open but will not be available for doing any merge/rebase or change. |
f93b4e5
to
a67be9b
Compare
🦋 Changeset detectedLatest commit: 9337691 The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
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 |
@silltho You're absolutely right. Allowing a PR from the community to sit for so long without being reviewed or merged is something I consider to be a failure on our part. We were dealing with 1.0 focus, multiple team members being rather busy at work, and speaking for myself quite a bit of burnout, but those aren't good excuses when other work was still being merged. We will do better in the future. In the meantime, I rebased this PR with changes from @allcontributors please add @silltho for code |
I've put up a pull request to add @silltho! 🎉 |
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 good to me! Love the clean prop getter function 💖
Pull request checklist
Please check if your PR fulfills the following requirements:
/start features)
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Fixes: #804
What is the new behavior?
FormControl
propagates props down toNumberInput
children.Does this introduce a breaking change?
Other information
I couldn't find any tests between FormControl and Select. So do i have to test the composition between FormControl and NumberInput?