You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if you could write relationships as:
type User implements Node {
name: String
posts: =AUTHORED=> Post
}
instead of:
type User implements Node {
name: String
posts: Post @relationship(path: "=AUTHORED=>")
}
This puts the arrow in a place that feels more natural and better matches Cypher.
It would be easy to define a preprocessing step that converts the first syntax into the second before passing to the graphlq-js parser. I 100% prefer the first syntax, but am concerned about compatibility w/ other tools if we introduce syntax extensions.
On the other hand, having a base schema that gets prepended already could make this difficult so maybe there isn't that much to lose, and we can always write the complete translated schema to a file or something.
The text was updated successfully, but these errors were encountered:
I do like the prefix notation of decorators quite a bit better than postfix directives, but it looks like the spec will include directives (graphql/graphql-spec#90).
If we do break spec compliance, I'd like to go all the way to the cypher style infix arrows.
It would be nice if you could write relationships as:
instead of:
This puts the arrow in a place that feels more natural and better matches Cypher.
It would be easy to define a preprocessing step that converts the first syntax into the second before passing to the graphlq-js parser. I 100% prefer the first syntax, but am concerned about compatibility w/ other tools if we introduce syntax extensions.
On the other hand, having a base schema that gets prepended already could make this difficult so maybe there isn't that much to lose, and we can always write the complete translated schema to a file or something.
The text was updated successfully, but these errors were encountered: