Andreas Berger

The example above is taken from https://github.com/neo4j-graphql/neo4j-graphql/blame/3.5/src/test/java/org/neo4j/graphql/NestedNonNullTest.kt It was introduced by https://github.com/neo4j-graphql/neo4j-graphql/issues/80 This feature requires post processing in combination with e.g. `apoc.util.validate` As of now solving this issue has no...

The example you provided is an edge case that shows the limits of the chosen approach. I think, to get the example working, you have to collect all the required...

> I believe that it should be configurable for each GraphQL type do define what data will be always fetched from neo4j to provide sufficient context for additional custom Data...

There are two use cases: 1. You query a top level field (with custom resolver) and want to use some data from neo4j to compute the result. Here you need...

In the Javascript-API a [new `@computed` directive](https://neo4j.com/docs/graphql-manual/current/directives/#_computed) is used to solve this kind of issue. So this will be fixed after the API-Alignement is implemented (which I'm currently working on).

@yarc Can you please test with the current master to see if the problem persists? If so can you [provide a testcase](https://github.com/neo4j-graphql/neo4j-graphql-java/tree/master/core/src/test/resources/issues).

yes, we can add this, but: 1. the client does not expect additional fields that were not requested 2. the fragment may have additional fields (mapped as a property rather...

In the JS-lib for each branch (type) the complete projection will be returned seperatly

this means that for request: ```graphql { person { name ... on Actor { a } ... on User { b } } } ```` the js-lib will generate a...

Is there also a way to extract the common properties as well (`.name` in the example)