It looks like a schema does not work unless there is an "alias": metadata. I cannot tell if this is intended behavior, my guess is that it should act like the alias is equal to the name used in the plugInfo.json file.
In addition trying to make an alias that is equal to the name of any of the entries in the plugInfo.json file produces an error.
If this is intended behavior a fix to the documentation to say the alias is required would be helpful.
Steps to Reproduce
Edit a plugInfo.json file, change the name of one of the items to match its alias and delete the alias metadata.
Try to use the schema, it acts like it exists but is a blank prim.
Paste the alias back in but leave the name equal and you get an error about a name collision.
Description of Issue
It looks like a schema does not work unless there is an
"alias":
metadata. I cannot tell if this is intended behavior, my guess is that it should act like thealias
is equal to the name used in theplugInfo.json
file.In addition trying to make an
alias
that is equal to the name of any of the entries in theplugInfo.json
file produces an error.If this is intended behavior a fix to the documentation to say the
alias
is required would be helpful.Steps to Reproduce
plugInfo.json
file, change the name of one of the items to match itsalias
and delete thealias
metadata.alias
back in but leave the name equal and you get an error about a name collision.