Incomprehensible type mismatch with query generics about apollo-client HOT 3 CLOSED

This is because the return value of useQuery uses TData both in covariant and contravariant positions.

I'd recommend that you use TypedDocumentNode here and then let inference take over:

const getById = <TData>(gql: TypedDocumentNode<TData>, id: string) => {
  return useQuery(
    gql,
    computed(() => ({ id }))
  )
}

and then use it like

const result = getById(MyQuery, "1")

Assuming that your queries are typed correctly (and this is probably the single most important thing to do when using GraphQL with TypeScript!), everything should be typed correctly from there on.
Your manual annotations only add inconsistencies and possibly type erasure, so I'd try to avoid those.

That said, this still breaks the rule of hooks.

What is the real value here instead of just using

const result = useQuery(gql, computed(() => ({ id })))

in your component?

from apollo-client.

Thanks for the hint, I actually forgot about the concept of contravariance, also I was not aware that there is TypedDocumentNode.

I'm currently abstracting CRUD operations for a multitude of different entity types, where all come with their own queries and result / variables types, hence why I need some form of generic typing for - in this case - an ID-based single entity query. With your hint I got the typing down correct now though, so thanks a lot!

from apollo-client.

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Client usage and allow us to serve you better.

from apollo-client.