[
https://issues.apache.org/jira/browse/GROOVY-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752450#comment-17752450
]
Eric Milles edited comment on GROOVY-9510 at 8/9/23 3:42 PM:
-------------------------------------------------------------
There was a discussion of using a closure resolve strategy of {{OWNER_FIRST}}
in order to resolve static fields and properties of the enclosing class (see
GROOVY-9655). In this case, it is less of an issue since
{{PreconditionContext}} or {{RetryConditionContext}} only respond to a few
names.
was (Author: emilles):
There was a discussion of using a closure resolve strategy of {{OWNER_FIRST}}
in order to resolve static fields and properties of the enclosing class. In
this case, it is less of an issue since {{PreconditionContext}} or
{{RetryConditionContext}} only respond to a few names.
> DelegatesTo and similar for annotation member methods
> -----------------------------------------------------
>
> Key: GROOVY-9510
> URL: https://issues.apache.org/jira/browse/GROOVY-9510
> Project: Groovy
> Issue Type: Bug
> Reporter: Björn Kautler
> Priority: Major
> Labels: annotations
> Attachments: image-2023-08-04-11-04-29-834.png, screenshot-1.png
>
>
> If you have an annotation with a closure field like for example this in Spock:
> {code:java}
> @Retention(RetentionPolicy.RUNTIME)
> @Target({ElementType.TYPE, ElementType.METHOD})
> @ExtensionAnnotation(RequiresExtension.class)
> public @interface Requires {
> Class<? extends Closure> value();
> }{code}
> you can use it like
> {code:java}
> @Requires({ os.windows }){code}
> But I see no way to add IDE-hints for that closure like
> {{@DelegatesTo(PreconditionContext.class)}} as it is restriced to parameters.
> It would be nice if you could also annotate annotation member methods (and if
> IDEs would then support that too).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
