From b1d0c84377efcf018ebcc5e863cdc7e2b679b9f4 Mon Sep 17 00:00:00 2001 From: Nicco Date: Fri, 11 Oct 2019 11:40:54 +0200 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 565e581..663ce35 100644 --- a/README.md +++ b/README.md @@ -76,7 +76,7 @@ const Form = () => { ## 🤔 Motivation -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. +So why write yet another form utility you might ask? First off, I don't like the Formik approach. In my humble opition formik is 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)