formula-one
formula-one copied to clipboard
flexport
Strongly-typed React form state management
Currently `onValidation` doesn't communicate whether errors are actually visible or not. Based on the feedback strategy, it's possible there are errors that the user cannot see. This is awkward. Once...
Current APIs for seeing errors are inconsistent. There should be consistency between all ways to access errors that allow easy access to all errors as well as errors which should...
There has been some confusion on what a `Field` is. Renaming `Field` (possibly to `BaseField` or `AtomicField`) and doing a writeup on what a `Field` is should make this easier...
Some of the documentation is out-of-date and the overall structure is bad. We should clean this up. This goes hand-in-hand with the talk I'll be giving to FP eng, so...
This is a bad one. It can be solved by a similar approach to the validations rework in v0.2
And proper use of `FeedbackStrategy.Submitted`
`addField`, `removeField`, `addFields` and friends need a callback that fires after their completion
Ultimately this will use the `setState` completion callback. This is useful for submitting after making a change.