-
Notifications
You must be signed in to change notification settings - Fork 59
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
Abstract properties of Filter #44
Comments
So that would be for families and hosts? |
So far, yes. And any other mandatory properties we'll end up with. |
Reopening this due to # E.g.
for PluginClass in publish.plugin.discover():
plugin = PluginClass(instance)
assert plugin.hosts == ['maya']
# As opposed to:
for plugin in publish.plugin.discover():
assert plugin.hosts == ['maya'] And in cases where the plugin takes different arguments, such as the Selector taking a Context and the Validator taking an Instance, further checks has to be made prior to getting hosts and families. It'd be more efficient if we could check compatibility before doing any instantiation, as was the case prior to this adjustment. Thoughts? |
This has been restored to non-properties due to the above explanation. |
It just occured to me that the mandatory properties of Filter et. al. should really be abstract properties. E.g.
So that whomever implements a plugin, will also have to implement the properties. E.g.
At the moment, you could implement a plugin, but forget about these properties which would make your plugin not work.
The text was updated successfully, but these errors were encountered: