Describe the bug
In strict mode, Annotator should not make any changes on the target module, that may introduce new errors on downstream dependencies. Although Annotator is aware of possible errors in downstream methods for a generated getter by Lombok (getFoo()), but it is unaware of copying mechanism by Lombok that annotations on foo will get copied on getFoo as well. Hence, it might introduce an error in downstream dependencies.
Expected behavior
Annotator should be aware of annotations getting copied on generated getter methods for fields by Lombok. And reject a tree, if any of their getter is creating new errors in downstream dependencies.
Describe the bug In strict mode, Annotator should not make any changes on the target module, that may introduce new errors on downstream dependencies. Although Annotator is aware of possible errors in downstream methods for a generated getter by Lombok (
getFoo()), but it is unaware of copying mechanism by Lombok that annotations onfoowill get copied ongetFooas well. Hence, it might introduce an error in downstream dependencies.Expected behavior Annotator should be aware of annotations getting copied on generated
gettermethods for fields byLombok. And reject a tree, if any of their getter is creating new errors in downstream dependencies.Stack trace Not-Applicable.
OS (please complete the following information):
Additional context Not-Applicable.