You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
As referencing of other shema is used and not always there is necessary to use all keys from the referenced schema, it would be great to have ignore_keys attribute with list of keys which should be ignored. It means those will not be added into gui and not collected into settings data.
There is several instance where would this feature come handful.
Very good idea. We had a brief chat about it with @iLLiCiTiT and came to two tweaks with the proposal.
This feature should work for templates, rather than schemas. Schemas should stay purely for simplifying the structure, while templates are for usage in multiple places and already can carry some metadata that modify their behaviour
the ignored keys will need to be specified as a full relative path to the key so we can ignore keys that are deeper in the hierarchy. for example plugins/publish/key1
Description
As referencing of other shema is used and not always there is necessary to use all keys from the referenced schema, it would be great to have
ignore_keys
attribute with list of keys which should be ignored. It means those will not be added into gui and not collected into settings data.There is several instance where would this feature come handful.
Example of usage:
In this example only
argument_1
will be used.Referencing of schema:
Referenced schema content
some_referenced_shema.json
:The text was updated successfully, but these errors were encountered: