Michael Hunger

icon indicating a website link https://www.jexp.de icon indicating an email [email protected]

icon company JEXP + @Neo4j icon location Dresden, Germany icon location I love open software and the people that build it. I'm the caretaker of the Neo4j community and teach girls to code. Also JavaChampion, speaker, author.

Results 538 comments of Michael Hunger

Aggregation fields

oh yes, sorry that's not meant to work. it's passed as a map so you'd have to do explicitely implement it in something like `WHERE $filters.id = p.id OR ...`

Aggregation fields

Probably for now, we're working on a client-side solution for java middleware in https://github.com/neo4j-contrib/neo4j-graphql-java

Filter not working in a cypher field

yes dynamic fields are different, we have to figure out how to integrate them in a better way.

Not all api's generated automatically

Which ones exactly? Can you spell the missing ones out?

How to update and delete through build in _id

Unfortunately that is not yet possible and is also not advocated. You should use an id that can be used externally not an internal id.

How to update and delete through build in _id

e.g. you could use an id that uses a UUID

Graphql SDL, option to have autogenerated mutations return the type rather than a string

Sorry didn’t see your message. Did you try the experimental endpoint which does that. That will become the default with the next version.

filter arguments

It will be in the next release (3.3.0.2)

filter arguments

@Phosphor-zhl could you please test it?

Proper non-null handling

Regarding null-ness: https://medium.com/@calebmer/when-to-use-graphql-non-null-fields-4059337f6fc8 > This is a less obvious downside of non-null fields, but one you should consider nonetheless. Whenever an error happens in a non-null GraphQL field then that...