Channels
#graphql-kotlin
Title
# graphql-kotlin
j
Joe
05/29/2021, 1:33 AMIs there a way to use a 3rd party annotation (ie, one that I can't directly annotate with @GraphQLDirective) as a directive? If not, what would need to get built out to make that possible? (Does @Deprecated just have explicit special handling that makes that one work?)
d
Dariusz Kuc
05/29/2021, 2:10 AMIs there a way to use a 3rd party annotation (ie, one that I can't directly annotate with @GraphQLDirective) as a directive?no
If not, what would need to get built out to make that possible?current logic is closely tied to that specific directive so unsure whether we could update it to be more generic you could try adding additional directives using hooks (e.g. something potentially in
didGenerateGraphQLTypedidGenerateQueryFieldDoes @Deprecated just have explicit special handling that makes that one work?yes it has special handling as it is one of the built-in directives
j
Joe
05/29/2021, 5:17 AMOk thanks, that makes sense. Was thinking something like Jackson's mixins could be a way to do it, but probably not worth the amount of work it would be vs just creating another annotation.
s
Shane Myrick
05/29/2021, 6:08 PMI think you could get around it with the hooks, but the Kotlin wiring and setup would be better to use and more explicit that this annotation is a schema directive, instead of overriding what the original annotation was meant to be used for
j
Joe
05/29/2021, 6:35 PMYeah we were looking to use existing dropwizard auth annotations rather than create our own analogues for an auth directive, but not a big deal to create our own
4 Views