useQuery argument null exception when query is null/undefined and skip is true

[MichaelBurgess]

In 3.1.5 I could do something like this:

const getQuery = (type) => {
  if (type === "foo") {
    return fooQuery;
  }
  if (type === "bar") {
    return barQuery;
  }
  return null;
}

// type will eventually get a non-null value, but will initially be null
const query = getQuery(type);

// skip until the query is determined
const { error, loading, data } = useQuery(query, {
  skip: !query,
});

In this example, I don't know what query to use until I have a value for type, therefore the query is skipped until I do.

This worked fine in 3.1.5, but in 3.2.0 I now get this:

Argument of null passed to parser was not a valid GraphQL DocumentNode. You may need to use 'graphql-tag' or another method to convert your operation into a document.

I don't see anything in the release notes documenting this change, so unsure if it was intentional, or a side-effect of something else?

Initially I thought this was the skip issue again as per #6190 (comment), but it seems a little different now?

System:
  OS: macOS 10.15.6
Binaries:
  Node: 14.10.1 - /usr/local/bin/node
  Yarn: 1.22.5 - /usr/local/bin/yarn
  npm: 6.14.8 - /usr/local/bin/npm
Browsers:
  Chrome: 85.0.4183.102
  Firefox: 80.0.1
  Safari: 13.1.2
npmPackages:
  @apollo/client: 3.2.0 => 3.2.0

[msjonker]

Looks like this was caused by #6999

[hwillson]

It doesn't sound like there is an outstanding issue here, so closing. Thanks!