I just resolved some deprecation warnings in my build related to coercing implementation and then noticed the current user docs for creating custom scalars will lead users towards deprecated versions of coercing methods.
Current user docs https://www.graphql-java.com/documentation/scalars#writing-your-own-custom-scalars
Current java docs https://javadoc.io/static/com.graphql-java/graphql-java/21.0/graphql/schema/Coercing.html
This is not technically a bug so I'm filing under "other issue" as documentation debt
I just resolved some deprecation warnings in my build related to coercing implementation and then noticed the current user docs for creating custom scalars will lead users towards deprecated versions of coercing methods.
Current user docs https://www.graphql-java.com/documentation/scalars#writing-your-own-custom-scalars
Current java docs https://javadoc.io/static/com.graphql-java/graphql-java/21.0/graphql/schema/Coercing.html
This is not technically a bug so I'm filing under "other issue" as documentation debt