You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* update graphql-java to version 15
This is an old version of a core dependency used in most graphql related projects in java. If this dependency isn't updated then you have conflicts with incompatible transitive versions of graphql-java.
Unfortunately, it looks like a committer to graphql-java likes to make backwards a lot of uneccessarily incompatible changes to the library. So I had to make a lot of changes for this to compile and for the tests to pass. I had to do some archeology in the history of graphql-java to understand some of the changes.
* GraphQLType.name no longer exists. simplePrint(GraphQLType) is used instead
* GraphQLFieldDefinition is no longer a GraphQLType, but it looks like GraphQLFieldDefinition.originalType will get the type we are looking for.
* ScalarInfo.STANDARD_SCALAR_DEFINITIONS was replaced with ScalarInfo.GRAPHQL_SPECIFICATION_SCALARS_DEFINITIONS
* The value generic for the return type of GraphQLSchema.typeMap is now more specific so BuildingEnv's constructor had to change.
* ShemaPrinter lost some include methods. One was previously mispelled.
* DefaultSchemaPrinterComparatorRegistry became DefaultGraphqlTypeComparatorRegistry.
I had to make some changes to the tests to make them pass, which makes me quite uncomfortable with this. Please check these over to see if I should have made more changes. I'm going ahead with this because the overall functionality still seems legit. I have no idea why these were needed.
* In translator-tests1 'render values' I had to move the clauses of the where clause around. It mateches the order of the cypher params now, so it kind of makes sense.
* The one line GraphQL query no longer works. It had to be broken up to multilines in several tests.
* relationship-tests is a weird one. I changed the generated Cypher, but it makes more sense now. The relationship is player through memberships to team. So `playerMembershipsTeam: Team` makes a lot more sense than the original `playerMembershipsPlayer: Player`. It actually looks like it was incorrect originally.
* adjustments for graphql-java update
Co-authored-by: Andreas Berger <andreas@berger-ecommerce.com>
Co-authored-by: Michael Hunger <github@jexp.de>
0 commit comments