Introduce patched state update

[kettanaito]

Description:

Adjust Form state updates to be applied in patches. Event subscription listens to patched update events dispatched, accumulates them, and updates the Form state with the respective chunk information. This eliminates obsolete state properties, which are properties irrelevant to the occurring update (i.e. value property being updated during blur).

In comparison, previously, a value change event produced the entire next field state:

{
  value: 'nextValue',
  name: 'fieldOne',
  valid: true,
  ...
}

With patched state updates the value change event will produce only the following patch:

{
  value: 'nextValue',
  pristine: false,
}

The state patch is then deep merged via a single event handler into the existing Form state.

Tickets:

• Closes Reactive require not working properly on page load #352
• Fixes Changing values with form.setValues() in an onChange() handler removes reactive props #364
• Partially covers Handle concurrent state updates #268 and Patched values update of controlled fields result into obsolete state #295

Roadmap:

• Introduce synchronous way of applying state patches
• Introduce asynchronous way of applying state patches
• Deprecate Form.updateFieldsWith
• Deprecate Form.fieldsDidUpdate
• All tests are passing
  • Field unmounting
  • Touched: A field becomes touched after focus and blur
  • Form-wide errors: All test suits
  • Conditional schema (fixed by 93a9f37)
  • Reactive props
  • Reactive props (Single target): Adjust to cover Changing values with form.setValues() in an onChange() handler removes reactive props #364 and pass
• Obsolete value of value during field change (fixed by 223ed93)
• Simplified validation result reflection
• Fixed a bug that a field rule rejected with no error displayed, when the error was set in the messages
• Add integration scenario for error message for Field.props.rule error message (name/type/general)
• (Bug) "RangeError: Maximum call stack size exceeded" upon form.reset()
• Solve intermediate state composition issue (and recordUtils call signatures)

[kettanaito]

These changes may not fully solve the concurrency issue, but they prepare a great background for such concurrency handling, and open new possibilities of building detailed dev tools.

[kettanaito]

There is currently an issue with the value change, as it sometimes returns obsolete (accumulated) value after quick clean/type. This has been common before, and was solved, unfortunately this issue is back now.

Most likely there is an issue during field change/blur related to field state that is passed to the validation. Obsolete value most probably comes from the postponed validation.

Update: The issue was caused by the Form.validateField method returning the entire next state of a field. That conflicted with the properties that didn't need an update (i.e. value), and resulted into obsolete state. I've fixed it to return only the next state patch, and the concurrency issues with value updates are gone for good.

[kettanaito]

Although patched state updates eradicate field value concurrency issue that required to have a delay set while typing into inputs during tests, it still doesn't help with random integration tests failing during their CLI execution. That matter may require more investigation, and I don't plan to do that as a part of this pull request.

[kettanaito]

I've tried to simplify record utils as a part of function call signature adjustment, and I can conclude that indeed a lot of payload coming into utility functions can be omitted, or replaced with the existing payload. I can't say it's perfect now, but some complicated utils (updateValidityState) where drastically simplified, removing the need for intermediate states.