Andreas Marek
Andreas Marek
Hi, I am one of the maintainer of [GraphQL Java](https://www.graphql-java.com). The GraphQL Java tutorial by @kaqqao is unfortunately outdated and also uses some third party libraries on top of GraphQL...
We have a hook called `beginFieldListComplete` which is called during the completion phase for List. But we don't have any hooks for `beginObjectComplete` or `beginScalarComplete` or `beginEnumComplete`.
In `QueryDirectives` everything returns a list of directives (because repeatable). But in `GraphQLDirectiveContainer` we have `getAppliedDirective` which returns just one. We should make them consistent.
This adds a new structure called `PreNormalizedQuery` and `PreNormalizedField` which is a query without variables. Note: this naming is outdated "PreNormalized" will be "normalized".
This change leverages the normalized query structure to collect the merged subfields instead of calling `collectFields` on demand. This aims to improve the performance for especially large and deep queries...
This PR adds automated performance tests. Every JMH test is executed on a fresh AWS EC2 instance and then the results are compared to previous results to make sure GraphQL...
Every single Ast Element has `SourceLocation` which is probably too much. It is only needed for errors and consumes a lot of memory unused otherwise. We should think of ways...
RuntimeWiring is very silent at the moment when you configure it wrong: a wrong type or not existing field registered is just accepted. This leads often to subtle problems, especially...