Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Clarification on built in support #37

Closed
@vigie

Description

@vigie

Hey there, just trying out the latest:

@graphql-codegen/typed-document-node@1.17.9

with

apollo-angular@2.0.3

and

@apollo/client@3.1.3

Observations:

Contrary to the documentation there doesnot appear to be build in support inapollo-angular@2.0.3. Here is a snippet of the d.ts that ships with that release, you can see thatTData is not being passed through toWatchQueryOptions:

watchQuery<TData,TVariables=EmptyObject>(options:WatchQueryOptions<TVariables>):QueryRef<TData,TVariables>;query<T,V=EmptyObject>(options:QueryOptions<V>):Observable<ApolloQueryResult<T>>;mutate<T,V=EmptyObject>(options:MutationOptions<T,V>):Observable<FetchResult<T>>;subscribe<T,V=EmptyObject>(options:SubscriptionOptions<V>,extra?:ExtraSubscriptionOptions):Observable<FetchResult<T>>;

In addition, support isnot added toapollo-angular by runningpatch-typed-document-node.

As expected, there is no built in support for@apollo/client@3.1.3. But when the documentation states that it is built in as of3.2.0 - does it mean that installing one of the betas is sufficient (since3.2.0 is not actually released yet)?

Support for@apollo/client was successfully added by runningpatch-typed-document-node`.

Thanks again!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp