Why ApolloStore#remove does not trigger changes to ApolloStoreWatcher? Should I publish an event manually with publish method?

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

Intended outcome:
This is more a docs problem more than anything. The docs include a recipe for using TransferHttpCacheModule to cache requests when using SSR but it does not work as the module does not support POST requests and has no intention to support it. See [here](https://git

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/

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

This is related to issue #552 . The previous PR solved most of the mismatches, but in the current snapshot (0.9.1+20-40e9f3a2-SNAPSHOT) arguments in root level operations still do not match.

Example

object Operations {
  @GQLDescription("query root")
  case class query_root(
      posts: PostsArgs => zio.UIO[List[Post]]
  )
}

case class Query_rootPostsArgs(
    ...
)

I

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