This work adheres to a new dogma in regards to view model data change reactivity - previously, input components (such as a text field, number spinner, drop-down and so on) would directly modify a TransientDocument's data. However, this made it very difficult to perform intermediary data transformations. Now, the new approach is to instead have these input components modify data on their owning view model instance. The data changed is kept behind ObservableFields, which offer an API for reacting to the data change and for transforming the data, before it is persisted. This new approach shall introduce a much stronger decoupling of the view model data and the actual data, which will make it easier to work with both.
Custom health states can now also have a limit defined.
TransientDocument's data. However, this made it very difficult to perform intermediary data transformations. Now, the new approach is to instead have these input components modify data on their owning view model instance. The data changed is kept behindObservableFields, which offer an API for reacting to the data change and for transforming the data, before it is persisted. This new approach shall introduce a much stronger decoupling of the view model data and the actual data, which will make it easier to work with both.