Passing {fields, values} to a form constructor will cause fields defined for those properties in values which are not defined in fields. This is not always wanted. For example, when the form is just for editing some parts, which is defined by fields, of the values that comes from somewhere not controlled by the UI developers. I suggest to define a new option fallbackFields with default value true. For those scenarios like the above, it is set false. If this idea is acceptable, I am going to create a pull request.
Passing {fields, values} to a form constructor will cause fields defined for those properties in values which are not defined in fields. This is not always wanted. For example, when the form is just for editing some parts, which is defined by fields, of the values that comes from somewhere not controlled by the UI developers. I suggest to define a new option fallbackFields with default value true. For those scenarios like the above, it is set false. If this idea is acceptable, I am going to create a pull request.