Trait Support

[tantaman]

[tantaman]

This is the case where multiple nodes should share a common interface and the schema maintainer would like to create an edge to that interface rather than the concrete nodes.

An alternative implementation would be to do this as union types rather than traits or interfaces.

E.g.,

Foo as Node {
} & OutboundEdges {
  things: Edge<Bar.fooId | Baz.fooId | Woo.fooId>
}

One problem is how to model that underlying query. If all three types are completely disjoint, what filters do we give the user to use?

Even if they are not disjoint, how do we generate the query type?

Do we inspect each type, collect together common properties, expose those as where methods?

And for the SQL storage -- do we only select fields that are compatible with a union operator? And once we get the return we re-query based on ID to fully hydrate each node?

^-- all said problems exist in the trait world too except that we don't have to walk types during code generation.

An option in the trait world is to return only the data that fulfills the trait.. This will create hella problems for caching and row level privacy, however.