Clint Ayres

@webholics u interested in putting together a PR? I will prioritize this work otherwise.

At this point I think we should stick with async validation. I do see what you mean about lifecycle's here. There may be a declarative solution in here, I think...

I'm a little confused by the wording, but I'll do my best to help; please clarify if I misinterpret what you are asking. First - Which version of this library...

@Mottoweb here is the [source](https://github.com/jurassix/react-validation-mixin/blob/master/spec/components/Signup.js) to the demo if that helps you out.

Ok I can reproduce this too. I can get the correct response when i ask for a single element like: `$r.props.isValid('username')` The bug seems to be inside the validator: https://github.com/jurassix/react-validation-mixin/blob/master/src/components/validationMixin.js#L89...

oops looks like it in here instead: https://github.com/jurassix/react-validation-mixin/blob/master/src/validationFactory.js#L22 I'm taking a look to see if anything odd stands out.

Ok this is probably inside the validator. I'm seeing the following: When I focus on Username field and then blur away: `$r.props.errors = {username: ['"Username" must be a string']}` Then...

We could handle this with a change to isValid to check that all values are empty or fix this up stream in the validator. I'll take a look at the...

Sure! Submit PR, I'll review and publish.

@georgebbbb technically onChange is a property of your Component and should really be something similar to this: ``` js const props = { value: 123, onChange: this.handleChange.bind(this), } ``` Update:...