halcyondude
commented
2 years ago after doing a bit of research, a few things are clear.
- the data model is best described via GraphQL
- data is likely best loaded via GraphQL mutations
- graphql type definitions generated using the Introspector nicely handle constraint and index declarations
- a VERY nice workflow using arrows.app exists.
- generate data model (as we've done) using arrows.app
- export as .graphql
- write the schema --> Neo4j DB using the neo graphql v3 library
Game Changer
https://neo4j.com/docs/graphql-manual/current/type-definitions/interfaces/#_directive_inheritance
Any directives present on an interface or its fields will be "inherited" by any object types implementing it. For example, the type definitions above could be refactored to have the @relationship directive on the actors field in the Production interface instead of on each implementing type as it is currently:
interface Production {
title: String!
actors: [Actor!]! @relationship(type: "ACTED_IN", direction: IN, properties: "ActedIn")
}
type Movie implements Production {
title: String!
actors: [Actor!]!
runtime: Int!
}
type Series implements Production {
title: String!
actors: [Actor!]!
episodes: Int!
}
interface ActedIn @relationshipProperties {
role: String!
}
type Actor {
name: String!
actedIn: [Production!]! @relationship(type: "ACTED_IN", direction: OUT, properties: "ActedIn")
}https://neo4j.com/docs/graphql-manual/current/type-definitions/interfaces/#_overriding
In addition to inheritance, directives can be overridden on a per-implementation basis. Say you had an interface defining some Content, with some basic authorization rules:
interface Content
@auth(rules: [{ operations: [CREATE, UPDATE, DELETE], allow: { author: { username: "$jwt.sub" } } }]) {
title: String!
author: [Author!]! @relationship(type: "HAS_CONTENT", direction: IN)
}
type User {
username: String!
content: [Content!]! @relationship(type: "HAS_CONTENT", direction: OUT)
}
type PublicContent implements Content {
title: String!
author: [Author!]!
}
type PrivateContent implements Content
@auth(rules: [{ operations: [CREATE, READ, UPDATE, DELETE], allow: { author: { username: "$jwt.sub" } } }]) {
title: String!
author: [Author!]!
}
AlexxNica
GraphQL schema --> source of truth
Tasks
[x] #52
[x] MVP CNCF Schema
[x] use schema to drive data model instantiation --> neo
Moved to new/other issue(s):
More Info
resources