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
Since a schema property can be shared it can create a single-source for configurations. As such, one area where this applies well is allow; it's accepted values and any metadata associated with those, for example:
Maintaining enums in a separate location for the allow "keys" ([ 'prog', 'comp', 'arch' ]) presents the challenge of maintaining this in multiple locations.
Proposed Solution
Currently allow supports either a string or an array. The proposal would be to expand this to also allow an object:
The above would simply process to allow the keys of the object as values, but the whole object could then be maintained in a lib (or in the model) and shared easily.
The text was updated successfully, but these errors were encountered:
Since a schema property can be shared it can create a single-source for configurations. As such, one area where this applies well is
allow
; it's accepted values and any metadata associated with those, for example:Maintaining enums in a separate location for the
allow
"keys" ([ 'prog', 'comp', 'arch' ]
) presents the challenge of maintaining this in multiple locations.Proposed Solution
Currently
allow
supports either astring
or anarray
. The proposal would be to expand this to also allow an object:The above would simply process to
allow
the keys of the object as values, but the whole object could then be maintained in a lib (or in the model) and shared easily.The text was updated successfully, but these errors were encountered: