Vladimir Razuvaev
Vladimir Razuvaev
We experimented a little bit with a custom `@mask` directive, which works similar to `@skip` at the cache reading level. This proved to be a pretty simple implementation (just a...
@jerelmiller Thanks for your response, let me reply inline > We've had discussions about the approach here and realize that an opt-out solution adds a bit of investment up-front, especially...
@hanlindev `useFragment` without [data masking](https://github.com/apollographql/apollo-client/issues/11666#issuecomment-2084911396) will be definitely an overhead. The repro doesn't seem to use `@nonreactive` directive, but I suspect the result will be similar even with it. We...
One way to go with it (that is also generic enough) is to allow custom field transformers in sourcing config here: https://github.com/gatsbyjs/gatsby-graphql-toolkit/blob/d3fd0879bbe958d7b97f04dddad2f76d05f7d960/src/create-schema-customization/transform-fields/field-transformers.ts#L27
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...
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...
@kdichev Makes perfect sense to me. I was going to add something like this in the future. But I am also open to a PR. So if you're up to...
Technically the toolkit just provides you the tools and you use them in gatsby APIs you need. In other words, the toolkit user should take care of calling `createSchemaCustomization` and...
@kdichev Thanks for the feedback! This is on my radar. We will probably remove the reporter or make it optional.