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
Currently, one can use any framework annotation in any place where annotation target allows, but this "odd" usages are not validated by the framework. For example, if one uses @Conditional on a class without an inject constructor or on a builder input, or anywhere else, Yatagan won't complain, it will simply ignore such usages, because it never queries anything besides @Component annotation.
Querying all the framework annotations to validate their usage is a prudent thing to do, yet it can penalize code generation performance and build "incrementality".
The solution would be to introduce an annotation processing option, specific to the codegen backends, that enables such extensive validation. Such option can be enabled in environments less sensitive to build performance and incremental rebuilds, like CI checks.
The text was updated successfully, but these errors were encountered:
Currently, one can use any framework annotation in any place where annotation target allows, but this "odd" usages are not validated by the framework. For example, if one uses
@Conditional
on a class without an inject constructor or on a builder input, or anywhere else, Yatagan won't complain, it will simply ignore such usages, because it never queries anything besides@Component
annotation.Querying all the framework annotations to validate their usage is a prudent thing to do, yet it can penalize code generation performance and build "incrementality".
The solution would be to introduce an annotation processing option, specific to the codegen backends, that enables such extensive validation. Such option can be enabled in environments less sensitive to build performance and incremental rebuilds, like CI checks.
The text was updated successfully, but these errors were encountered: