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.

Sign up for GitHub

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

Jump to bottom

Version 0.1.0 #4

Merged
merged 33 commits into from
Nov 5, 2021
Merged

Version 0.1.0 #4

merged 33 commits into from
Nov 5, 2021

Conversation

nikhilag
Copy link
Contributor

@nikhilag nikhilag commented Oct 7, 2021 •
edited
Loading

This is a major milestone for this form library for handling complex form requirements with ease. Here's a quick overview of what was changed:-

  • Using new features of recoil 0.4.1 to do transactions to allow multiple atoms to be updated safely and together
  • Got rid of snapshots wherever possible to improve performance. In some places, useRecoilCallback still needs to be used because useRecoilTransaction doesn't allow returning data.
  • Allow any level of nesting with help of optional ancestors for fields for field arrays. Note that only field arrays can be ancestors of fields. This means everything is now handled recursively since a field or field array can have as many ancestors.
  • Code refactoring.
  • Switched to useEffect in individual atom instead of relying on atom naming to figure out how to construct the final object. Also to allow multiple forms to work together, formId is generated internally. There's still room for improvement here but overall a step in the right direction.
  • Support for defaultValue in useFieldArray
  • Initial support for react native

dev-rishi-witbybit and others added 29 commits August 31, 2021 13:29
@dev-rishi-witbybit
add polyfill for string.matchAll
4e99ca6
@nikhilag
Remove polyfills.js and import type for matchAll polyfill
37b8dad
@nikhilag
v0.0.20-1
c66d518
@nikhilag
Breaking change for managing fields inside field array
fe8dcac 
- Introduce fieldArrayName, index as optional parameters to be used with useField() inside field array
- Use matchAll from core-js
- Delete Controller since there is no use case currently. Compatibility with other form libraries can be explored in near future
@nikhilag
Move to dts-cli from tsdx since tsdx is not active currently
e0a4e5f
@nikhilag
Fix test failure
cb68241
@nikhilag
v0.0.20-2
6b70f01
@nikhilag
Breaking Change: Use fieldArrayInfo optional prop for capturing field…
f43d708 
… array info in field
@nikhilag
v0.0.20-3
1ee88b4
@nikhilag
Allow multiple ancestors, use transaction, use effect to track values
68e5ee4
@nikhilag
Fix missing dependency warnings
1d7a0e6 
Note that Recoil setters have been added as dependencies for useEffect or useCallback - facebookexperimental/Recoil#472
@nikhilag
v0.1.0-0
42396f8
@nikhilag
Add support for multiple form components
b3c89ca
@nikhilag
v0.1.0-1
b16f438
@nikhilag
Switch to useRecoilCallback for returning value in getFieldArrayValue()
273725d
@nikhilag
v0.1.0-2
3347c2b
@nikhilag
Fix bugs for validateData and remove in field array
9be2649
@nikhilag
v0.1.0-3
28b0acf
@nikhilag
Bug fixes
79e728c
@nikhilag
v0.1.0-4
85c75de
@nikhilag
Add support for filtering fields in field array selector, use ancesto…
4349f66 
…r's skipUnregister, bug fixes
@nikhilag
v0.1.0-5
e476f19
@nikhilag
Bug fixes for final values
6481aa4
@nikhilag
Add type for field (to be removed later)
8d87837
@nikhilag
v0.1.0-6
0cc8aa4
@nikhilag
Allow ancestors for watching fields + fix field array watch
9a81f71
@nikhilag
v0.1.0-7
b7eee73
@nikhilag
Add useFormContext and defaultValue for field array
03fdf97
@nikhilag
v0.1.0-8
7902ad5
@github-actions
Copy link

github-actions bot commented Oct 7, 2021 •
edited
Loading

size-limit report 📦

Path Size
dist/react-recoil-form.cjs.production.min.js 11.67 KB (+132.8% 🔺)
dist/react-recoil-form.esm.js 11.76 KB (+128.56% 🔺)

@nikhilag nikhilag merged commit 3d49831 into main Nov 5, 2021
@nikhilag nikhilag deleted the multiple-ancestors branch November 5, 2021 03:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@nikhilag @dev-rishi-witbybit