-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client filter by annotation #2280
Conversation
*/ | ||
public HttpClientFilterResolver( | ||
@Parameter @Nullable Collection<String> clientIdentifiers, | ||
@Parameter @Nullable AnnotationValue annotationValue, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There might be multiple filters with customer stereotype
annotations. Taking into account we are passing information about just one annotation into resolver, is it correct to assume Micronaut will not support a case when multiple client annotations are applied on a client?
For example with a current implementation apparently it won't be possible to do something like
@Metered @OauthClientCredentials @Client() SomeClient client
, correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@svishnyakoff Currently that is correct. If you'd like to create a separate issue for the enhancement of the feature that would be OK
Could you resolve the conflicts? |
No description provided.