Does typed-document-node replace some typescript-react-apollo features?

[miller-productions]

Hi there,

I hve just come across typed-document-node and wondering if it replaces some features from typescript-react-apollo?

For example, in one of the code examples we see that the approach is to work with useQuery from @apollo/client.

Would this replace the approach of working withHooks from typescript-react-apollo?

[miller-productions]

Reading this discussion #4580 , I suspect the answer is yes: you probably don't need typescript-react-apollo if you are using typed-document-node.

@dotansimha mentions it here

Did I interpret that correctly?

[dotansimha]

You are right, the question is yes. But note that it depends on adoption in actual libraries (or patches we provide here: https://github.com/dotansimha/graphql-typed-document-node).

There are limitations, since we can't offer new features on the generated code, and it all depends on implementing clients.

In terms of development, we are still maintaining typescript-react-apollo (and others) and we'll keep doing that, since it's heavily used.

[miller-productions]

Thanks Dotan,

So, if a library that you are using has built-in support then you should be ok to start using typed-document-node.

However, if the library you are using doesn't yet have built-in support, then you will be required to patch in order to use typed-document-node.

That is helpful. Much appreciated.