-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
CustomDirective for smallrye-graphql does not work #20802
Comments
I attached a sample project to reproduce the issue (or you look into my sample repo https://github.com/johgoe/quarkus-sample-20802/blob/main/src/main/java/org/acme/ ) |
Hi @johgoe - Thanks for this. Yes we are still working to get this into Quarkus. We expect to have it in soon. |
@phillip-kruger was it implemented somehow or it's still pending? |
Not yet. On my todo list... |
hi @phillip-kruger it's still pending? |
still pending. PRs welcomed |
Describe the bug
It seems that types of custom directive annotations are not added to the deployment, which causes an error on startup, if the directive is used in a entity.
I'm not familar with quarkus extensions but it seems that in SmallRyeGraphQLProcessor getSchemaJavaClasses() all Types which are used in Schema are added except the Types of the Directive. I guess a single line like
will fix my problem.
Expected behavior
Quarkus is starting even if I use custom directives within my GraphQL API
Actual behavior
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.2.3
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: