Enhancement: Publisher allow actions even when no failure occurred #736
Labels
community
Issues and PRs coming from the community members
type: enhancement
Improvement of existing functionality or minor addition
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
The Pyblish API actions allow defining actions for Plugins on different states, e.g.
on = "failed"
but alsoon = "all"
, like:all
: Alwaysprocessed
: After plug-in has been processedfailed
: After plug-in has been processed, and failedsucceeded
: After plug-in has been processed, and succeededI'd actually like these to also be available in the New Publisher UI.
We're looking to e.g. add an action for succeeded published to be able to run actions even on successful publishes (preferably per instance; even though that is not Pyblish native behavior).
For example, in the Publish Success report page we'd love to be able to:
This originated from artists requesting:
By exposing Pyblish's actions API and functionality 1 to 1 this would become easily possible.
How would you imagine the implementation of the feature?
Similar to publish validation report pages the Publish Report (before full publish, but on successful validation) and the Publish Success Report pages would also show the actions per instance.
For easy access it'd also be preferred to be able to right click the instance left hand side to pick the actions there instead of requiring to select the individual plug-ins.
Psuedocode could be:
Are there any labels you wish to add?
Describe alternatives you've considered:
An alternative approach is to allow Pyblish Plugins to inject e.g. custom actions into
instance.data["actions"]
or even ainstance.actions
attribute so that we can actually apply actions per instance instead of per plug-in. That way e.g. a plug-in could expose it to only those instances that have any published instances, e.g.:Additional context:
No response
[cuID:OP-7357]
The text was updated successfully, but these errors were encountered: