Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Warning when creating foo and foo:includes collections #3251

Open
johnhaddon opened this issue Aug 27, 2024 · 1 comment
Open

Warning when creating foo and foo:includes collections #3251

johnhaddon opened this issue Aug 27, 2024 · 1 comment

Comments

@johnhaddon
Copy link

johnhaddon commented Aug 27, 2024 •
edited
Loading

As discussed in https://forum.aousd.org/t/guidance-for-api-schema-instance-names/1498, USD issues a warning if both foo and foo:includes collections are authored on the same prim. This can be seen by executing the following example code :

stage = Usd.Stage.CreateInMemory( "test" )
prim = stage.DefinePrim( "/Test" )
Usd.CollectionAPI.Apply( prim, "foo" )
Usd.CollectionAPI.Apply( prim, "foo:includes" )
Usd.CollectionAPI.GetAllCollections( prim )

Which yields the following warning :

Warning: in _PropertyTypesMatch at line 257 of /.../primDefinition.cpp -- Cannot compose schema specs: Schema relationship spec at path '/CollectionAPI.collection:__INSTANCE_NAME__:includes' in layer 'anon:0x7f4f19446080' is a different spec type than schema attribute spec at path '/CollectionAPI.collection:__INSTANCE_NAME__' in layer 'anon:0x7f4f19446080'.

It would be great if this restriction could be removed.
@jesschimein
Copy link
Contributor

Filed as internal issue #USD-10033

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@johnhaddon @jesschimein