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

Explicit targets not registered globally #364

Merged
merged 12 commits into from
Mar 21, 2020
Merged

Explicit targets not registered globally #364

merged 12 commits into from
Mar 21, 2020

Conversation

buddly27
Copy link
Contributor

@buddly27 buddly27 commented Mar 9, 2020

This resolves #363 and #345

pyblish/logic.py Outdated Show resolved Hide resolved
Copy link
Member

@mottosso mottosso left a comment

Choose a reason for hiding this comment

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

Taking another look at this, and my initial doubts was in changing logic.Iterator by adding the targets argument. But I think that's the way to go. Before, it kept up to date with tagets by looking globally, but that was no good. Now it's being handed targets directly, which I think is right.

Have a look at my minor notes, and then I think we can merge this. Good job.

pyblish/logic.py Outdated Show resolved Hide resolved
pyblish/util.py Outdated Show resolved Hide resolved
tests/pre13/test_logic.py Outdated Show resolved Hide resolved
@buddly27 buddly27 requested a review from mottosso March 20, 2020 19:47
@mottosso mottosso merged commit 010c630 into pyblish:master Mar 21, 2020
@mottosso
Copy link
Member

Thanks @buddly27!

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.

Explicitly use targets without global registration
3 participants