9 Matching Annotations
- Nov 2020
-
-
In principle, this information is already available through other means, but it is actually a fair amount of work to gather it in this form, and I think it could be useful to open it up to programmatic consumption.
-
- Oct 2020
-
www.basefactor.com www.basefactor.com
-
Focus on your application: forget about forms details like I'm dirty, field touched...
-
You can try to build a solution to tackle these issues on your own, but it will cost you time and money... why not use a battle-tested solution to handle all this complexity?
-
If you want to implement a form with a superb User Experience, you have to take care of many variables:
-
Form validation can get complex (synchronous validations, asynchronous validations, record validations, field validations, internationalization, schemas definitions...). To cope with these challenges we will leverage this into Fonk and Fonk Final Form adaptor for a React Final Form seamless integration.
-
Managing Form State (holding field information, check if a control has been touched, if the user has clicked the submit button, who owns the current focus...) can be tedious and prone to errors. We can get help from React Final Form to handle these challenges for us.
Tags
- too hard/difficult/much work to expect end-developers to write from scratch (need library to do it for them)
- difficult/hard problem
- fonk (form validation library)
- form design
- integration
- can't keep entire system in your mind at once (software development) (scope too large)
- tedious
- form validation
- a lot of things to consider
- don't write your own
- easy to get wrong
- complexity
- react-final-form
- form validation library
- reinventing the wheel / not invented here
- user experience
- adapter
Annotators
URL
-
-
github.com github.com
-
It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
-
- Sep 2020
-
-
There are work arounds, but nothing clean. I just feel like this should be functionality that should be part of the slot feature.
-
-
-
You must: reference each element you are extending using refs or an id add code in your oncreate and ondestroy for each element you are extending, which could become quite a lot if you have a lot of elements needing extension (anchors, form inputs, etc.)
Tags
- too hard/difficult/much work to expect end-developers to write from scratch (need library to do it for them)
- could be easier / more difficult than it needs to be
- scalability
- difficult/hard
- framework taking care of responsibility so users can leverage it and not have to worry about that responsibility themselves
- why this feature is needed
Annotators
URL
-