John

It seems like the most future proof solution to this problem is for auto-generated mutations to return a special mutation type. To start, the mutation type could have two fields...

Also, I really want to emphasize how AmAZiNg I think this plugin has the potential to be! The ability to automatically provision CRUD operations ***with CRUD operations for relations and...

While my server doesn't "crash," I can also report that union types are not working. The following schema: ``` CALL graphql.idl(' type Frog { id: ID! } type Cat {...

Discussion in #52 is related

👍 Tried to use a block string as shown in the example: ``` type Person { primaryEmailAddress(ownerId: ID!): PersonEmailAddress @cypher(statement: """ MATCH (perspective :OwnerInterface {id: $ownerId}) MATCH (this)-[:PERSON_PRIMARY_EMAIL_ADDRESS]->(email), (email)-[:PERSON_EMAIL_ADDRESS_VISIBLE_TO]->(perspective) RETURN...

Note, at the moment this can be pretty easily worked around using schema-stitching and transforming the neo4j database fields to be lowerCamelCase. If there's a good reason for the current...

Gotcha. So it's intended to distinguage auto-generated queries from custom user queries? It's not readily obvious to me how that's useful. As the person coding the user queries, I know...

Hmm, looking at some of the tests, looks like same goes for `MutationType` as well.

Oops, looks like I'm wrong in saying that the current format breaks the spec. The spec has an example with `type MyQueryRootType` as the root query type. While I'm still...

No worries! I actually saw that GraphConnect was happening and figured I wouldn't hear from anyone for a week or two 👍