Michael Hunger

you could try to add a type `Node` and a computed field with `@cypher` directive ``` others: Node @cypher(statement:"MATCH (this)-[*..4]->(b) return b") ``` you'd have to use fragments to differentiate...

Currently the plugin doesn't support date-time types yet. We will add it to the stand-alone neo4j-graphql-java library, which will be available through the /graphql/experimental endpoint.

Yes this is a shortcoming in the generation. We need to handle this if there are both in and out-relationships with the same name and end-type.

It should just work. The only way this fails right now I guess is that they are executed in an order where the relationship-creation is called before the node-creations/updates. So...

merge was added at least for types can you try again in the latest version? It seems that in graphql-java the fields were not executed in order because they were...

What would you suggest? Not send the stack-trace at all? Or rather the first few levels only. It's def. useful for debugging issues. And for handling in the client one...

What doesn't work well with your solution? (You missed the name parameter in HateBoy) You could also navigate along the relationship with a filter. ``` query { Boy(name:"Ahmed") { name...

Can you please try to use proper Markdown formatting for code in your issues? This makes it really hard to read them!

Lots of different questions. Perhaps you could split them into different issues. 1. graphql doesn't allow to refer to previous nodes higher up the tree 2. you're not filtering twice,...

What happens then? I tried to reproduce your issue with a test but couldn't see the problem: ``` @Test fun dynamicFieldArgParameter() { val schema = """ type Person { name:...