Upgrade to PostGraphile V5

[benjie]

Note that since PostGraphile V5 is still pre-release sponsors-only software right now, to use this PR you will need to know the secret from https://grafast.org/caveats/ . If you don't have access and are already a sponsor, ping Jem (on the Graphile Discord, via Twitter, or via email on their first name at graphile.com) and they'll help you get set up.

IMPORTANT: when viewing the diff, you should hide whitespace changes otherwise it'll look a lot bigger than it really is.

Any questions, ask me in #🔮 on Discord (if you can't see that channel, ping Jem - see above).

NOTE: CI is not passing, because CI is not a sponsor 😉

[benjie]

hookArgs is how the context is derived now, it means withPostGraphileContextFromReqRes is no longer needed. We pass the req/res objects (both into expressv4 and node scopes) so that hookArgs can use them to call your context callback (or pgSettings/additionalGraphQLContextFromRequest if you're using the V4 preset, which we are) to derive the GraphQL context.

[benjie]

The TypeScript types in V5 need improving so that this cast isn't needed 😅

[benjie]

It's now the responsibility of the next layer of plans to execute this. See the LoginPayload.user plan above, which is effectively:

    LoginPayload: {
      user() {
        const $userId = currentUserIdSource.execute();
        return userSource.get({ id: $userId });
      },
    }

[benjie]

This is an alternative approach if you know the database name rather than the inflected source name. I include it as an alternative to the much simpler equivalent code we saw before:

const userSource = build.input.pgSources.find((s) => s.name === "users");

[benjie]

The @pgSubscription directive is no more, instead write a subscribePlan (see below).