Query with `fetchPolicy: 'cache-only'` is not updatable via `updateQueries`

I have a query Sale that I don’t want to initially fetch and a mutation OpenSale with:

      updateQueries: {
        Sale: (prev, { mutationResult }) => console.log('test'),
      },

Intended outcome: Console prints ‘test’

Actual outcome: Nothing happens

How to reproduce the issue: Create a query with fetchPolicy: 'cache-only', try to update it in a mutation with updateQueries.

I’m trying to upgrade to 1.0.2 from 0.8.6. Previously I had noFetch: true and everything worked fine. Is it an expected behavior in 1.x or a bug?

[helfer]

You’re right, we could check what you pass against the definition in the query. That might be useful for client-side updates. What we can’t actually check is if the variables are of the correct type in the place where you use them.

I don’t think we want to get into the variable coercion business, but it’s good to know that we could, if we wanted to 😀

[helfer]

@Dattya yeah, that would definitely explain it! Apollo doesn’t coerce any variables you give it. Since we don’t have the schema on the client, so we can’t even check if they fit the definition. I can see how that would be useful though, so I’m thinking about adding the option to put some more schema information in the client in the future to be able to do validation etc. with it.