Describe the bug
Our GraphQL endpoint returns JSON in an specific structure, instead of the default data property, we only map our result into the data property when the operationName is IntrospectionQuery. But for some reason when loading the introspection query the value of operationName is null. Causing the result of the IntrospectionQuery to be on our custom JSON structu

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
     

Describe the solution you'd like
I'd like to use this project with Ktor but the documentation seems to be lacking for any framework other than Spring. I believe it would be nice to improve the documentation with some other Kotlin frameworks taken into account, Ktor being one of them. At least some getting started docs would be perfect.

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

Exceptions sub classes overrides toString instead of getMessage for instance in https://github.com/ghostdogpr/caliban/blob/master/client/src/main/scala/caliban/client/CalibanClientError.scala#L13

As a result when these exceptions are logged through SLF4J, the stack trace does not contain the actual error message. For instance I get:

caliban.client.CalibanClientError$CommunicationErr

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

Currently downloading the graphql schema is a requirement for babel-plugin-tag to work. It would be useful to specify an URL as an option to the file path.

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