Comments (3)
I'm personally not a big fan of this type of behavior being part of Formik. IMO embedded structures inside a field should be handled by encapsulated components that update the structure appropriately, not at the top Formik level. Making a DSL for updating arrays and objects adds a lot of complexity and idiosyncrasy to the Formik API.
from formik.
My suggestion was not to have a new methods but have the current methods that accept a string for the field name of the property to update, to be upgraded to do what they currently do with the same api but accept a field:string that can be a path too if the user wants.
To the current users nothing changes and there are no breaking changes, just a new option to path
this api stays the same --> handleChangeValue = (field: string, value: any) => {
//just the implementation inside changes
}
I am doing it on my side right now but if it goes inside formik my code would be more abstract and easier.
Now is the point were it is a decision on your part to were you want it to go. I gave my thoughts and hope it help to create new ideas at least.
I like your library because it almost doesn't demand me to do things one way.
from formik.
Lodash has not mutative version of all methods, it is the FP version.
https://github.com/lodash/lodash/wiki/FP-Guide
from formik.
Related Issues (20)
- Validation Error HOT 4
- handleChange can't target state values with delimiters
- Add correct types for `Field` HOT 6
- onPaste + setFieldValue does not work as intended HOT 2
- Get validating state of individual components
- Page reloads on submit if form is inside drawer component HOT 5
- Margin not added in UI HOT 3
- Uncaught (in promise) TypeError: e2 is null [CoreValidator.ts:138:2]
- Why do I have to specify a name again when using useField's onChange function?
- Support for React Native's SyntheticEvent type
- formik file upload handling HOT 4
- Consider shipping a LICENSE file with your npm package HOT 1
- useField's onChange function should accept non-string values as args
- Formik.dirty is not reacting to nested changes HOT 1
- Docs layout is a bit broken HOT 4
- React Native form resets to initial values
- Terneries, espescially deeply nested ternaries, make code difficult to read. Please do not do this. HOT 1
- RangeError: Maximum call stack size exceeded HOT 1
- Call formik.setFieldValue() with previous value as parameter
- Formik Validation
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from formik.