Chore: Use explicit plug-ins and orders from pyblish api instead of legacy plug-ins #304
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use explicit pyblish api orders, instead of order of legacy plug-ins
iLLiCiTiT
approved these changes
Mar 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog Description
Use explicit plug-ins from pyblish api instead of legacy plug-ins
Use explicit pyblish api orders, instead of order of legacy plug-ins
Additional info
This shouldn't change usage behavior but these are more explicit and by refactoring these older uses we're now making it more unified usage inside AYON by removing the legacy usage.
Only remaining usage seems to be in
./tools/pyblish_pype/mock.pyhereTesting notes: