You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the feature you have in mind and explain what the current shortcomings are?
We have to define limit up to which point it is possible to create or change context (folder, task, product type/name) of instances during publishing.
I've already created multiple issue related to this task in related repositories that do recommend to use order CollectorsOrder - 0.2 as last possible limit. We should focus to do it earlier (as soon as possible). That will unblock a lot of global plugins to run earlier and will avoid having plugins with order CollectorsOrder + 0.499999999 because is dependent on something else etc.
If I missed any integration then please create an issue, or modify existing.
How would you imagine the implementation of the feature?
Define the limit, use the limit in Publisher code to validate it, and possibly report the issue with warning in console (or other way), so developers can actually have a way how to validate if it happens or not (even I don't know where/when I do create instances or change it's context).
When we tackle most of the logic changes we can slowly change order of global plugins like CollectInstanceAnatomyData earlier to validate if it really works.
The text was updated successfully, but these errors were encountered:
Please describe the feature you have in mind and explain what the current shortcomings are?
We have to define limit up to which point it is possible to create or change context (folder, task, product type/name) of instances during publishing.
I've already created multiple issue related to this task in related repositories that do recommend to use order
CollectorsOrder - 0.2
as last possible limit. We should focus to do it earlier (as soon as possible). That will unblock a lot of global plugins to run earlier and will avoid having plugins with orderCollectorsOrder + 0.499999999
because is dependent on something else etc.This is a long run issue.
Relevant issues
If I missed any integration then please create an issue, or modify existing.
How would you imagine the implementation of the feature?
Define the limit, use the limit in Publisher code to validate it, and possibly report the issue with warning in console (or other way), so developers can actually have a way how to validate if it happens or not (even I don't know where/when I do create instances or change it's context).
When we tackle most of the logic changes we can slowly change order of global plugins like
CollectInstanceAnatomyData
earlier to validate if it really works.The text was updated successfully, but these errors were encountered: