Benjie
~~I'm very limited on time but I managed to make this basically work for the Graphile Engine codebase. No doubt there's going to be a bunch of cleanup, but I...
> Lee: Wrapping this up. Advice: Back up from proposal to redefine the problem. For input unions that was very helpful. A lot to like, but also opening up a...
> Action - goal: seems you've done an inwards-out approach that you're getting pushback from, maybe you should try an outside-in approach where you try and pull from people what...
### Feature description New users don't know that this is an option. Since it's the preferred option, we should make it the default when users `init`. ### Motivating example It's...
### Feature description We already have `--! no-transaction` special comment, and we have `:PLACEHOLDER` replacement... This feature would replace a `--! include funcs/my_func.sql` comment with the contents of the `funcs/my_func.sql`...
If the client issues `Accept: application/graphql-response+json, application/json` and the server does not support this for the request (e.g. the request uses `@stream`/`@defer` so needs a multipart response) then the server...
Essentially it needs the same as for TSconfig mentioned here: https://postgraphile.org/postgraphile/next/requirements#typescript-v500-optional Otherwise you get red squigglies in VSCode under the `import { ... } from "postgraphile/utils"` or similar import paths....
The polymorphism filtering support in #1817 only wants to add types to the enum that will exist at runtime. These types might be built but then it turns out that...
Also: export the default error masking function. Also: document how to log errors/etc (are there hooks for this?)