Release 0.14.0

• onChange now has a second argument that is true/false depending on there actually being a change from the initial values passed to the form elements (thanks @sdemjanenko)
• You can now pass an object to reset to reset to specified values (Thanks @tomaash)
• Check out http://twisty.github.io/formsy-react-components/playground/ and https://github.com/twisty/formsy-react-components (Thanks to @twisty)
• Some internal bugs
• Added new prop: preventExternalInvalidation which does not invalidate inputs where external errors are set (Thanks for discussion @pkmiec and @ordinathorreur!)
• You can now use "address.street" as a name and the resulting model will be {address: { street: 'foo' } } (Thanks for discussion @kristian-puccio, @ivome, @ntucker, @LeoIannacone and @ppiekarczyk)
• Now supports passing any form value to the internal form via Formsy.Form, like "autoComplete"

0.13.1

• Fixed validation rules to support "none existing value" (Thanks to @sdemjanenko)
• Fixed bug with complex object as value
• Fixed bug with isFormDisabled on dynamic inputs (Thanks for report @mloginov)
• Added more tests

0.13.0

• Changed development environment to run tests in Node. CI running tests on deploy and added indication on Github
• Fixed bug with passing objects/arrays as values (Thanks for reports and examples @simiographics)
• Added reset method to Formsy Form (Thanks @erwanjegouzo)
• Added isFormSubmitted method to Formsy Elements (Thanks @erwanjegouzo)
• The standalone release is now one minified file with sourcemaps

0.12.6

• Fixed bug with passing values from validation rules
• Lots of new tests for validation rules (Thanks to @erwanjegouzo)

0.12.5

• Fixed an issue where you pass validation errors with the "invalidate" callback on onSubmit and onValidSubmit. When changing the inputs all errors would disappear, but not anymore. Only the current input error will disappear and any validation rules running on the input will take over

0.12.4

• Formsy compared the validations passed to a form element in case the form decided to suddenly change the validation rules on a form element. Dynamic validations is a really weird concept, I do not believe anyone is using it and it gets a bit troublesome when you now can pass objects as validations. Decided to remove them. This caused a bug using objects as validations an rerendering the component handling the form

0.12.3

• Fixed required bug (Thanks for report @dprentis)

0.12.2

• Git is not nice to me with the invalidate callbacks for onValidSubmit and onInvalidSubmit. They are back and tests are written to avoid this happening again (Thanks for reporting @pkmiec)

0.12.1

• Removed novalidate from form. This was a misunderstanding. Added formNoValidateto readme as this is a React property to avoid validation on submit of input types with native validation

0.12.0

• Important! From version 0.12.0 Formsy only supports React 0.13.1 and up
• Fixed warning of overrided props. Formsy now uses a cloning method (Thanks for tip @jmartin84) to handle passing Formsy props, but this will change to parent-child context in React 0.14.0, which gives better performance
• Validations "isEmail", "isAlpha", "isWords" and "isSpecialWords" now validates to true when not having a value. Use "required" to invalidate a "non-value" (Thanks for pointing this out @dprentis)
• Cleaned up some code
• By default "novalidate" is added to form to avoid native validation. You can change this with <Formsy.Form novalidate={false}/> (Thanks for suggestion @dprentis)