Feat: a way to avoid certain references about gatsby-graphql-toolkit

[Leksat]

I tried to make my idea to work, but it looks like it's too much of work. And the result would look like a hack (in comparison with the current toolkit code).

I think it should be easier for me to adjust the Drupal's schema. I mean switch to GraphQL module version 4 and write custom schema/resolvers.

[vladar]

Hey, I did a draft of the drupal sourcing using the toolkit here: https://github.com/vladar/gatsby-source-drupal-graphql

But it does create a separate node for each translation using a fragment like this for id:

fragment MyIdFragment on SomeDrupalType {
  __typename
  entityId
  entityLanguage {
    id
  }
}

[Leksat]

Oh! I thought that the ID fragment should have __typename plus one ID field. Didn't know that multiple ID fields are allowed. Looks like I misread the docs 🤦
Thanks for the hint!

So I guess this issue can be closed?

BTW, we switched our Drupal Gatsby Toolkit prototype to GraphQL module version 4. And we won't go back to v3 🙂 Here is why: https://github.com/AmazeeLabs/silverback-mono/tree/development/apps/silverback-drupal#why-not-version-3-of-drupal-graphql-module

[vladar]

We had to update the toolkit to support nested fields in id fragments (as it turned out to be useful). You can use as many fields as needed for gatsby ids.

But keep in mind that for "delta sourcing" you will need to provide all of the id fields and a proper NODE_ query to re-fetch individual translations.