Although I’m the biggest fan of repairs, I am seeing more and more why the current repairing system isn’t working when having them in production.
This may be my fault, but I’m finding that I need an order of repairing instances. Currently if you instruct artists to hit “Repair” when they find them, they will do so in the order they see them in the UI.
The problem with this is that if you have two validators working on top of each other. Case study is these two validators;
ValidatePathExistence: This plugin validate whether the directory of the instance output exists.
ValidatePathLocation: This plugin validate whether the directory of the instance output is correct.
When the artist sees this in the list, they might create unnessecary directories when the path location is uncorrect to begin with but artist sees the repair button for the path existence first.
This is a simple example to get the idea across, but its a growing problem with increasing amounts of repair methods on instances.
I’m an advocate of getting a system in place for repairing, as it will speed up production but maybe I should wait for the “Event Driven Processing” feature; https://github.com/pyblish/pyblish/issues/143