Skip to content

[3.6.5] - Custom Schema Hooks / graphql-java-datetime #920

Answered by dariuszkuc
rowi1de asked this question in Q&A
Discussion options

You must be logged in to vote

Hello 👋

As you noticed, underlying issue is due to the fact that graphql-java types do not implement hashcode/equals so if you try to add the same type twice it will blow up. I haven't looked too deep into the linked graphql-java-datetime library but it looks like it has autoconfiguration that will attempt to automatically register those extended scalars which in turn conflicts with your schema hook declaration.

Since in order to generate the the valid schema you need to explicitly provide those mappings in the hooks, I believe that if you disable the graphql-java-datetime autoconfiguration class it should work as well.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@rowi1de
Comment options

Answer selected by smyrick
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #920 on October 26, 2020 15:12.