Feature requests

Based on the documentation at https://graphql.org/learn/execution/#root-fields-resolvers, I expected that resolvers would always receive the parent/previous object as the first argument. However when I tested the library, the arguments received by the resolvers are actually (args, context, info).

This doesn't match the documentation, and is a serious limitation when one

I'm submitting a ...

• bug report
• [ X] feature request
• question

PostGraphile version: 4.4.4

postgraphile should honor variables in query string as defined in https://github.com/graphql/express-graphql#http-usage when the query is provided as post body.

with the following exampl

Update

The website is now live under a new domain 🎉

https://typegraphql.com/

This is the last domain change I hope 😄

Background

The typegraphql.ml domain from Freenom has expired (or cancelled because I had no reminder on email as usual!), so the docs site is not reachable by this URL.

Freenom has marked typegraphql.m

I have an interface with multiple implementing types. Two of these types happen to share a property that is not in the interface. This property is calculated from the data in the same column in the table for both types so each type uses sqlDeps in the field data passed to join-monster. When I query the interface and use fragments to get this overlapping property (among others unique to each type

Question:

The documentation states:

but 3.x.x is shipping. Is 3.x.x or 2.x.x preferred?
Is there a post or a set of release notes that describe the difference between 2.x.x and 3.x.x?

Environment:

apollo-client 2.6.8, React Native, Cognito, RN 61, Expo SDK 36

using Authorization and Su

There should be documentation for explaining the server side code, as well as the folder structure. Even though it is inherited from create-react-app, some kind of documentation should be present.
Steps to Reproduce
NA
I would like to work on this.

We should add type annotations for all definitions except those in tests, and enforce this with a mypy.ini configuration like this:

[mypy]
python_version = 3.8
...
disallow_untyped_defs = True

[mypy-tests.*]
disallow_untyped_defs = False

Hello,

I used to use Prisma alot with Apollo, and I'd like to completely replace Prisma with Cruddl, but I have a few questions:

• Is there a typeDefs generation for Cruddl as Prisma does (https://www.prisma.io/docs/prisma-cli-and-configuration/cli-command-reference/prisma-generate-xcv2/)

The reason for asking this is because currently (as far as the docs go), I'd have to setup a GraphQL

Do you have an example to do caching to avoid too many calls to the Api by using data-loader or apollo-server v2 datasource?

We're on 1.0.0-beta.11. I'm trying to require inner joins on some queries to limit the result set. It looks like almost-full-stack/graphcraft#34 covers it. Is that the case? If so, how can I use an inner join in my query? For example:

{
  Design (
    where: {
      customerId: 2635
    }
  ) {
    id
    name
    DesignLocations {
      loca