Skip to content

Conversation

@kosam0913
Copy link

Goal: to let developing pyblish plugin be more developer friendly (sort of)
Motivation: same as above~

Modifications:

  1. add context and instance as class Plugin's attributes (not only a arguments)
  2. append repair and other customize method into Plugin.actions during instantiation
  3. add context and instance as class Action's attribute (for further data transfer)

1. convert context and instance from argument to class attribute
2. append repair and other customize method into Plugin.actions
This reverts commit 24ff0ca.
1. add context and instance as Plugin attr so user no need to care about arguments while developing plugin

2. add context and instance to Actions, so action can communicate with rest data

3. append repair and other custom action into Plug.actions while Plugins are created.
@mottosso
Copy link
Member

Thanks for this @kosam0913, welcome to Pyblish. :)

The most important aspect of developing for Pyblish is to maintain backwards compatibility, so have a look at what AppVeyor is complaining about first of all.

Second would you be able to provide some examples of what your changes would mean? Some usage examples, along with some of the problem this addition solves. What problem should a developer be having to benefit from this change?

modify for compatibility of python<3.5
add back Plugin.repair for test_plugin
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