Is your feature request related to a problem? Please describe.

• Many projects include a JS target. Supporting JS targets will increase Apollo’s viability when being considered for multi-platform projects.
• It is not straightforward to use Apollo in projects that include a JS target. This is due to the apollo-runtme-kotlin artifact, which can’t be used in commonMain. One workaround is

Description

Graphql clients comparison (apollo client vs graphql-hooks vs urql).

Suggested implementation

List describing the advantages / disadvantages to other major clients. This library looks interesting but I don't see any advantage other file size.

The docstring of expectOne says

   /**
     * Expect that a single  has been made which matches the given URL, and return its
     * mock.
     *
     * If no such  has been made, or more than one such  has been made, fail with an
     

Is your feature request related to a problem? Please describe.
Currently we don't have any integration tests that verify that generated federated GraphQL schemas are valid with the Apollo Gateway.

Describe the solution you'd like
One of the PR hooks (Github Action?) start up the example federation apps (including gateway) and verify federation works.

Additional context
Related

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
On most of my React-Native screens that contain more than one Query, only the first one ever gets loaded and rest are stuck on loading forever. I can confirm from AppSync logs that no network requests are ever made for those queries. They also never return an error and are simply stuck. Using the A

version: 0.9.5

I'm generating client code and the output gives circular references:

[error] /home/gui/automat/wp-graphql-woocommerce-scala/src/main/scala/client.scala:40749:20: illegal cyclic reference involving type RootQuery
[error]   type RootQuery = RootQuery
[error]                    ^
[error] /home/gui/automat/wp-graphql-woocommerce-scala/src/main/scala/client.scala:42184:23: 

Type: minor

Describe the bug
After adding a new account address, the screen goes blank you appear to be logged out, but when you refresh the page, the address is there and you are still logged in.

To Reproduce
Steps to reproduce the behavior:

1. Go to storefront
2. Log in
3. Click user name in upper right > Profile
4. Add a new address.
5. When you submit the form, see the

Loving this project.

I feel like this project would benefit from a short quick start tutorial that demonstrate common methods such as:

Create item

    mutation = Operation(schema.Mutation)  # note 'schema.'
    mutation.create_item(input=dict(id="23432")).__fields__()

List items with filter

    op = Operation(schema.Query)  # note 'schema.'
    op.list_it

The fix for #509 enables using graphql interfaces and sub types in the client. However, it does so in a way that creates partial record accessors.

https://github.com/AlistairB/morpheus-repro/tree/partial-fields demonstrates the issue. stack build will produce the warning (it uses m