Describe the bug
The method contracts of Coercing allows for only Coercing*Exceptions to be thrown out of them. But, when the implementations only implement the deprecated versions of the methods using the latest graphql-java, and invoke non-deprecated versions of the APIs with any null values, there is a possibility for AssertionExceptions to be thrown.
Is this an expected behavior? And is it allowed to throw such validation exceptions?
To Reproduce
Use any Scalar from https://github.com/graphql-java/graphql-java-extended-scalars and invoke the non-deprecated API's with null values.
Describe the bug
The method contracts of Coercing allows for only Coercing*Exceptions to be thrown out of them. But, when the implementations only implement the deprecated versions of the methods using the latest graphql-java, and invoke non-deprecated versions of the APIs with any null values, there is a possibility for AssertionExceptions to be thrown.
Is this an expected behavior? And is it allowed to throw such validation exceptions?
To Reproduce
Use any Scalar from https://github.com/graphql-java/graphql-java-extended-scalars and invoke the non-deprecated API's with null values.