Should it be required to set the "errors" property to be able to use this component?

[notmessenger]

Presently if you do not set this property you will get an error (not from a guard clause). It seems reasonable that a "simple, down-and-dirty" form experience is desirable in some instances and error management is not anything needed. Do we then add logic to all of the form components that interact with the error object to not do so if it's not set or do we direct developers who do not wish to leverage the error features to simply provide an empty object to the property?

The former provides a cleaner API to the user and is "nicer", the latter is easier on us, less moving parts, etc.