81 enable passing initialvalue to usefieldprops #84
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MiroslavPetrik
force-pushed
the
81-enable-passing-initialvalue-to-usefieldprops
branch
from
080121a
to
f98efa1
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #84 +/- ##
==========================================
+ Coverage 89.44% 89.45% +0.01%
==========================================
Files 92 92
Lines 2217 2220 +3
Branches 183 183
==========================================
+ Hits 1983 1986 +3
Misses 231 231
Partials 3 3 ☔ View full report in Codecov by Sentry. |
github-actions bot
pushed a commit
that referenced
this pull request
Jan 18, 2024
## [4.0.7-next.3](v4.0.7-next.2...v4.0.7-next.3) (2024-01-18) ### Bug Fixes * **useDateFieldProps:** make dateField initializable via options ([#84](#84)) ([164487d](164487d))
|
🎉 This PR is included in version 4.0.7-next.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
MiroslavPetrik
added a commit
that referenced
this pull request
Jan 18, 2024
* fix(useFieldProps): enable passing initialValue via options (#82) * chore(release): 4.0.7-next.1 ## [4.0.7-next.1](v4.0.6...v4.0.7-next.1) (2024-01-18) ### Bug Fixes * **useFieldProps:** enable passing initialValue via options ([#82](#82)) ([4fb0c3f](4fb0c3f)) * fix(checkboxFieldProps): make checkboxField initializable via options (#83) * chore(release): 4.0.7-next.2 ## [4.0.7-next.2](v4.0.7-next.1...v4.0.7-next.2) (2024-01-18) ### Bug Fixes * **checkboxFieldProps:** make checkboxField initializable via options ([#83](#83)) ([63afa6d](63afa6d)) * fix(useDateFieldProps): make dateField initializable via options (#84) * chore(release): 4.0.7-next.3 ## [4.0.7-next.3](v4.0.7-next.2...v4.0.7-next.3) (2024-01-18) ### Bug Fixes * **useDateFieldProps:** make dateField initializable via options ([#84](#84)) ([164487d](164487d)) * fix(useNumberFieldProps): make numberField initializable via options (#85) * chore(release): 4.0.7-next.4 ## [4.0.7-next.4](v4.0.7-next.3...v4.0.7-next.4) (2024-01-18) ### Bug Fixes * **useNumberFieldProps:** make numberField initializable via options ([#85](#85)) ([dbad7da](dbad7da)) * fix(useFilesFieldProps): ignore the initialValue (#86) (#87) * chore(release): 4.0.7-next.5 ## [4.0.7-next.5](v4.0.7-next.4...v4.0.7-next.5) (2024-01-18) ### Bug Fixes * **useFilesFieldProps:** ignore the initialValue ([#86](#86)) ([#87](#87)) ([40362f0](40362f0)) * fix(useTextFieldProps): make textField initializable via options (#88) (#89) * fix(useTextFieldProps): make textField initializable via options (#88) * optional options fixes #88 * chore(release): 4.0.7-next.6 ## [4.0.7-next.6](v4.0.7-next.5...v4.0.7-next.6) (2024-01-18) ### Bug Fixes * **useTextFieldProps:** make textField initializable via options ([#88](#88)) ([#89](#89)) ([10d8ea9](10d8ea9)) * fix(useSelectFieldProps): make field initializable via options (#91) * chore(release): 4.0.7-next.7 ## [4.0.7-next.7](v4.0.7-next.6...v4.0.7-next.7) (2024-01-18) ### Bug Fixes * **useSelectFieldProps:** make field initializable via options ([#91](#91)) ([126b454](126b454)) * fix(RadioGroup): support for `initialValue` prop (#92) (#93) fixes #92 * chore(release): 4.0.7-next.8 ## [4.0.7-next.8](v4.0.7-next.7...v4.0.7-next.8) (2024-01-18) ### Bug Fixes * **RadioGroup:** support for `initialValue` prop ([#92](#92)) ([#93](#93)) ([f08db15](f08db15)) * fix(useCheckboxGroup): make field initializable (#94) (#95) fixes #94 * chore(release): 4.0.7-next.9 ## [4.0.7-next.9](v4.0.7-next.8...v4.0.7-next.9) (2024-01-18) ### Bug Fixes * **useCheckboxGroup:** make field initializable ([#94](#94)) ([#95](#95)) ([412f651](412f651)) * fix(useMultiSelectFieldProps): make field initializable via options (#96) (#97) fixes #96 * chore(release): 4.0.7-next.10 ## [4.0.7-next.10](v4.0.7-next.9...v4.0.7-next.10) (2024-01-18) ### Bug Fixes * **useMultiSelectFieldProps:** make field initializable via options ([#96](#96)) ([#97](#97)) ([049945b](049945b)) --------- Co-authored-by: semantic-release-bot <[email protected]>
github-actions bot
pushed a commit
that referenced
this pull request
Jan 18, 2024
## [4.0.7](v4.0.6...v4.0.7) (2024-01-18) ### Bug Fixes * make fields initializable ([#98](#98)) ([2cd4e76](2cd4e76)), closes [#82](#82) [#82](#82) [#83](#83) [#83](#83) [#84](#84) [#84](#84) [#85](#85) [#85](#85) [#86](#86) [#87](#87) [#86](#86) [#87](#87) [#88](#88) [#89](#89) [#88](#88) [#88](#88) [#88](#88) [#89](#89) [#91](#91) [#91](#91) [#92](#92) [#93](#93) [#92](#92) [#92](#92) [#93](#93) [#94](#94) [#95](#95) [#94](#94) [#94](#94) [#95](#95) [#96](#96) [#97](#97) [#96](#96) [#96](#96) [#97](#97)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.