The version is the same on both sides but the files are different.
But with complex forms, mixing this logic with other ones make the code implicit and difficult to understand very quickly.
I had not considered it - I was only thinking of mapping to the final user object model that I want to submit.
With this, our component is now capable of setting the value of a property in a form.
Later will elaborate more on the strategy of how to handle the config file and its location.
We would like to be able to add this component to a form in a very similar way to how we add a standard HTML input to a form, by either adding the formControlName or ngModel directives to it: We would also like for this component to be compatible with the built-in validators, and use them to make the field mandatory and set a maximum value: But in the case of the current version of our control, if we would try to do so we would get an error: ERROR Error: Must supply a value for form control with name: 'totalQuantity'.