I think the client-side URL routing on your docs website is broken?

Reproduction:

1. Go to https://www.apollographql.com/docs/react/
2. In left hand menu click "Api Reference" then "class ApolloClient"
3. client-side JS pushes the URL "https://www.apollographql.com/docs/react/api/apollo-client/"
4. reload page
5. get a page not found error

I think the URL should be something like: "http

Issue

Installation instruction listed on this web page advises to place $(SRCROOT)/YourTarget/**/*.graphql into Input Files to prevent unnecessary recompilations.

I discovered that API.swift is not regenerated if one of the graphql files is modified.

Diagnosis

It looks like globstar is not respected. Tested with Xc

I can't this lib to initialize, because it can't find variable 'self'

I'm running the following:
"expo": "19.0.1",
"graphql-request": "^1.3.4",
"react": "16.0.0-alpha.12",
"react-native": "https://github.com/expo/react-native/archive/sdk-19.0.0.tar.gz"

plus a babel-preset-expo preset

After closing #1082, I've seen that we are missing documentation on ResponseFetcher API. The JavaDocs on this API is actually quite good 👇

https://github.com/apollographql/apollo-android/blob/master/apollo-runtime/src/main/java/com/apollographql/apollo/fetcher/ApolloResponseFetchers.java

We should add more info about this into caching.md docs.

apollo-link-ws comes with the 'graphql-ws' Sec-Websocket-Protocol header.
I would like to change tha

Package

graphql-hooks

Environment

• graphql-hooks version: 4.3.0
• react version: 16.12.0
• Browser: Chrome

Description

I noticed the data variable returned from useQuery is undefined when first rendering a component. This collides with the fact that the types say it's always defined.

See index.d.ts:

interface UseClientRequestResult<ResponseDat

We just need a piece of documentation because there is literally no documentation about directive locations except from the spec. The spec is not easy to read. Something like this would make sense

directive @field_definition on FIELD_DEFINITION
directive @argument_definition on ARGUMENT_DEFINITION
directive @object on OBJECT
directive @interface on INTERFACE

interface Foo @inter

Question:

The documentation states:

but 3.x.x is shipping. Is 3.x.x or 2.x.x preferred?
Is there a post or a set of release notes that describe the difference between 2.x.x and 3.x.x?

Environment:

apollo-client 2.6.8, React Native, Cognito, RN 61, Expo SDK 36

using Authorization and Su

The documentation home page today is just the Getting Started page. We could create a docusaurus landing page so we can have a more visual appealing site to view and that is SEO friendly.

See: https://docusaurus.io/

Developing on the default config with localhost:3000 is fine.

However when I tried to test the local dev version from a device in the local network, say 192.169.110.1:3000, one of the client requests is still pointing to localhost:3000. Specifically, it's http://localhost:3000/__meteor__/dynamic-import/fetch, which makes the app unresponsive/unable to login from devices other than localhost.

With the following schema:

schema {
  query: Queries
}

type Post {
  similar(limit: Int!, offset: Int): [Post!]!
}

type Queries {
  users: [User!]!
  posts: [Post!]!
}

type User {
  similar(limit: Int!): [User!]!
}

SchemaWriter will generate 2 case classes named SimilarArgs that clash with each other.

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

First of all thank you very much for your awesome package! ))

In Json.Decode module there is a function lazy which helps with building recursive encoders. Please define in your module GraphQL.Request.Builder the same function or explicitly explain in module docs how to deal with recursive decoding and encoding, because it confuses inexperienced Elm developers.

An example

After

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.

Is there a plan to implement field-level documentation?

It's not super typesafe, but honestly providing a function of String -> Maybe Text that is called with each field inside the GQLType class could work.

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