Bret Patterson
Bret Patterson
I've provided a very simple sbt project that reproduces this problem. [by-name-repro.zip](https://github.com/mockito/mockito-scala/files/8529596/by-name-repro.zip) In the reproduction project, similar to my actual scenario but simplified, the scenario is as follows: I have...
There are some limitations in the handling of input types because of the shortcut used in the GraphQLObjectMapper.getInputType copying the existing ```equivalent``` outputType. We need this functionality such that getInputType...
* Upgrade to graphql-java 3.0.0 * Minimum JVM version 8 * Remove JODA dependency in mainline package and use standard java 8 Optionals instead.
Change the ITypeNamingStrategy Interface to use seperate input/output naming strategies. IE: ``` String getInputTypeName (..) String getOutputTypeName(..) ```