Update README.md

This commit is contained in:
Nicco 2019-10-11 11:29:05 +02:00 committed by GitHub
parent 6a50d8b02d
commit c1b58bec3f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -76,7 +76,7 @@ const Form = () => {
## 🤔 Motivation ## 🤔 Motivation
So why write yet another form utility you might ask? First off, I don't like the Formik approach. It's very verbose and in my humble opition very verbose. Also does not work with hooks. [react-hook-form](https://react-hook-form.com/) is a very cool library and it is the main inspiration for formhero. It does almost everything right... typescript, no deps, small, concise. The problem that I found while using it was that 3rd party ui libs like ant-design or fabric ui do not always have the standart `onChange` or `value` props in their components. That is where react-hook-form starts falling apart. This is what formhero tries to address in the most minimalistic way possible, with as little code as needed. All in pure typescript and no deps. So why write yet another form utility you might ask? First off, I don't like the Formik approach. In my humble opition very verbose and requires lots of boilerplate. Also does not work with hooks. [react-hook-form](https://react-hook-form.com/) is a very cool library and it is the main inspiration for formhero. It does almost everything right... typescript, no deps, small, concise. The problem that I found while using it was that 3rd party ui libs like ant-design or fabric ui do not always have the standart `onChange` or `value` props in their components. That is where react-hook-form starts falling apart. This is what formhero tries to address in the most minimalistic way possible, with as little code as needed. All in pure typescript and no deps.
## 🔥 Examples [(More Here)](https://github.com/CupCakeArmy/formhero/tree/master/examples) ## 🔥 Examples [(More Here)](https://github.com/CupCakeArmy/formhero/tree/master/examples)