ent
ent copied to clipboard
lolopinto
right now it's annoying because of the way things work. basically have to drop the edge and recreate it. or hack the edgeType to reuse the old one obviously can't...
useful for migrations or things of that ilk
task to add comment to the top of each generated object about where it's defined: * actions * edges * ents * edge actions * graphql objects etc
* ent implementation should be storage agnostic. it should be a consistent API that clients can implement * will come with 3 implementations out of the box * memory [redundant...
high level way i'm thinking of it is way to move code in observers to a queue and have the queuing system pick up after the mutation would speed up...
we currently support scalars but it's not well documented. don't support directives
instead of `canViewerSee`, `canViewerDo`, `canViewerEdit` etc might make sense to have a configurable `__metadata` field that developer can hook into to add their own types|fields which returns fields and values...