As a user, I am noticing a number of features that are not in parity with the native Homebridge implementation of the config.schema.json for the form based configuration user interface.
This issue deals with non-working creation of titles from the property names of certain sections or nested levels. By default this is a feature that is turned on in the Angular version:
"by default schema form uses the property name in the schema as a title if none is specified, set this to true to disable that behavior"
This does not seem to be the same experience with the Vue.js implementation. I also don't know if this is a "will not fix" issue, because it is easily fixed if there is a child "title" property for that section. But it was nice not having to have that there for simplicity's sake.
As a user, I am noticing a number of features that are not in parity with the native Homebridge implementation of the config.schema.json for the form based configuration user interface.
This issue deals with non-working creation of titles from the property names of certain sections or nested levels. By default this is a feature that is turned on in the Angular version:
https://github.com/json-schema-form/angular-schema-form/blob/master/docs/index.md#global-options
This does not seem to be the same experience with the Vue.js implementation. I also don't know if this is a "will not fix" issue, because it is easily fixed if there is a child "title" property for that section. But it was nice not having to have that there for simplicity's sake.