busypeoples
busypeoples
Thanks for the feedback, will have a look.
You need to change the `isGreaterThan` function, which is being run immediately as you're calling it with `isGreaterThan(5)`. Change it to accept two arguments like ` a => b =>...
Yes, it makes sense to handle invalid rules. Instead of throwing an error we can handle it differently. In dev mode we can issue a console warning. Added a warning...
Thanks for the feedback, will try to see how we can approach this as soon as I have some time. Should find some time this week!
Yes, I can see why this is confusing. This doesn't work `initialState={{name: 'foo'}}`? Passing in `initialState={ form: ....}` will break, should be `initialState={{ form: {name: 'foo'} }}` to not break,...
I think there are two reasons why this is confusing: 1.) `initialState` implies that one can pass in more than the actual form field values. That's why `initialState` should be...
The rules object is is the problem: `const validationRules = { name: [[notEmpty, 'Name cannot be empty']]}`
Yes, good point. We'll add some dev logging mechanism and sane defaults. Regarding TS and Flow, yes - let's add them.
@alexcroox Will have a look at the problem. I would say that you're using the revalidation `onChange` not the one you passed down via props. ``` const Form = ({...
``` const Form = ({ revalidation : { form, onChange, updateState, valid, errors = {}, onSubmit }, onSubmit: onSubmitCb, submitting = false, onFormChange, }) => ( ``` and then use...