-
Notifications
You must be signed in to change notification settings - Fork 129
Conversation
Did some quick preliminary testing in Maya. Launches fine, seems to work at first sight. I guess it's just a debate about those last potentially unused methods whether it's worth removing those too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As these are not used anywhere and it survived my casual playing with Maya I guess it is safe to merge it.
Any verdict on these still remaining functions that appear unusued? openpype.hosts.maya.api.lib.without_extension
openpype.hosts.maya.api.lib.remove_id
openpype.hosts.maya.api.lib.unique_name
openpype.hosts.maya.api.lib.no_refresh |
Is |
No, that is - how confusing it might seem - If we'd want there's also |
I would remove them too. Even if they might be useful later, I hate idea to have OP as repository for useful but not used code :) Anyway, we have git history and if needed, they can be resurrected. |
Agreed. Removed with b52e511 Did some preliminary testing in Maya 2020. Still seemed fine, as expected! 👍
Even better now. ♻️ |
Woop woop! -2932 lines! |
Brief description
First pass at cleaning up some dead Maya integration code, as a step for #1306
Notes
The following functions also appear unused - but I wasn't sure whether to remove them.
The
remove_id
might be nice to keep in the API for anyone coding against the OP maya integration. Thewithout_extension
I wasn't sure about because it was exposed in the__init__
for the API too. The other ones feel like some that we can remove too?Also, some of the removed code came from Avalon core and had no use in OP.
Testing notes
Still needs to be tested in Maya.