Phil Pluckthun

This is odd. While I expected a linking issue, this currently does not reproduce. I'm expecting that this could be related to an installation + `expo-modules-autolinking` scanning going wrong. I...

Just to add this as a side-note for arguments on directives themselves to be typed or rather for GraphQLSP to recognise them, the schema that's passed to GraphQLSP/`gql.tada` has to...

In your specific example, what stops you from matching the type on `{ pageInfo: PageInfoLike, edges: readonly EdgeLike[] }`, for example? Since the directive needs to annotate a field and...

Can you clarify your setup please? This really seems like an oddity of your own project. For instance, take our examples in this repo. They're pretty standard Vite projects and...

> when I ran gql.tada doctor it didn't give me any errors It likely won't if you use both `references` and then put `compilerOptions` in the same `tsconfig.json`. The problem...

This has been missing multiple things from our [contributing guide](https://github.com/urql-graphql/urql/blob/main/CONTRIBUTING.md) We at least need a changeset to be able to merge this, which is a changelog entry file that describes...

> The use-case is to be able to use more effective methods for serialize/deserialize That's self-evident, but also imprecise. This is basically the [XY Problem](https://xyproblem.info/). I understand already that you...

Two small concerns here: - If this is run on every SSR request the extra cost of running this may outweigh the benefits in many cases since JSON operations in...

In what context are you using GraphQLSP? If it's in the context of `gql.tada`, then we could consider lowering it to an `info` level, which should make it less intrusive,...

oh, I wasn't aware that we highlight the entire document. That should definitely be adjusted as well. I don't think we want to really mark the entire document in this...