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.

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

usdShade: Add ShaderValidator #3398

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

beersandrew
Copy link
Contributor

Description of Change(s)

  • Added equivalent validation checks from ARShaderChecker in the new ValidationFramework, including validation implementation code, test code, tokens, and an entry in plugInfo.json

Link to proposal (if applicable)

Fixes Issue(s)

Checklist

[X] I have created this PR based on the dev branch

[X] I have followed the coding conventions

[X] I have added unit tests that exercise this functionality (Reference:
testing guidelines)

[X] I have verified that all unit tests pass with the proposed changes

[X] I have submitted a signed Contributor License Agreement (Reference:
Contributor License Agreement instructions)

- Added equivalent validation checks from ARShaderChecker in the new ValidationFramework, including validation implementation code, test code, tokens, and an entry in plugInfo.json
shaderInput.GetAttr().GetPath().GetText(),
sources.size())
);
continue;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tallytalwar one note here, I noticed this was not present in the other validator here however:

  1. We do get a warning below when calling GetConnectedSource since with multiple sources we should call GetConnectedSources
  2. It appears GetConnectedSource gets the first connected source, so the complianceChecker code would not be validating issues for other connected sources

Happy to change this and loop through the connected sources if you think it's better to add that logic in, it made sense to me to stop checking since no matter what the connections were, it seems invalid to have more than one. Let me know if that's incorrect.

@jesschimein
Copy link
Contributor

Filed as internal issue #USD-10396

@jesschimein
Copy link
Contributor

/AzurePipelines run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants