Please describe the feature you have in mind and explain what the current shortcomings are?
After introducing the has_promised_context attribute for creating context instances (introduced here), we no longer need to warn users that a required context does not exist during the publishing process in the CollectAnatomyInstanceData plugin.
Users might be confused by the warning icon because it suggests there's something wrong with the publishing context, but everything is actually fine.
How would you imagine the implementation of the feature?
We should have the instance data transient key has_promised_context available. This would allow us to change the logging switch from warning to info type in case of an exception.
Are there any labels you wish to add?
[X] I have added the relevant labels to the enhancement request.
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
After introducing the
has_promised_contextattribute for creating context instances (introduced here), we no longer need to warn users that a required context does not exist during the publishing process in theCollectAnatomyInstanceDataplugin.Users might be confused by the warning icon because it suggests there's something wrong with the publishing context, but everything is actually fine.
How would you imagine the implementation of the feature?
We should have the instance data transient key
has_promised_contextavailable. This would allow us to change the logging switch from warning to info type in case of an exception.Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
The image is taken form testing during https://github.com/ynput/ayon-resolve/pull/15.