Benjie

Okay if you're not using the Relay preset then `node_id` column name will conflict with the default `nodeId: ID` field. It'll give you a conflict error though: ``` graphile-build:warn Recoverable...

We should add a diagnostic for this to tell people to either: 1. Use the relay preset (such that `nodeId: ID!` becomes `id: ID!` instead) 2. Rename the column in...

I wasn't able to find how you managed to get it to give the error you listed.

Simplify inflection plugin does indeed not factor in `_schemaPrefix`. Doing so would need a major version bump of that plugin, and integration into the tests. I'd be happy for someone...

My instincts tell me this is an issue in this function: https://github.com/graphile/crystal/blob/dc0d44696d929f2ffcb8725e5bcf9951db937cb1/utils/graphile-export/src/optimize/index.ts#L41 If you replace that function with: ```ts export const optimize = (inAst: t.File, runs = 1): t.File =>...

We have the beginnings of this already in the form of `fixtures` - you would manage your views/procedures/RLS policies/GRANTs/etc in fixtures, and then `--!include` them from `current.sql`. What we lack...

Quick message because it's Saturday, and preface: I have never once used Hasura so don't know it's layout or anything. Sounds like you're pretty close! One option is instead of...

You could also just write the plans yourself, they're not that complex. Have a look at the exported schema around specifically these fields.

Hey @zxpectre, how's it going? Can I offer any further guidance?

Put on hold because I need to stop fiddling and get V5 out. Can change this later.