Query returns null for invalidated entity instead of reexecuting

[myieye]

I've got this query. The return type is a nullable Project:

query projectPage($projectCode: String!) {
  projectByCode(code: $projectCode) {
    id
    name
    code
  }
}

When I invalidate the matching project:

cache.invalidate({__typename: 'Project', id: args.input.projectId});

Then the next execution of the query still hits the cache (cacheExchange) and returns null.
I want it to hit the server, because a new project might have been created with the corresponding code.

I think I read somewhere that this is probably, because projectByCode is allowed to return null.
Is that correct? If so, are there any elegant ways to "properly" invalidate the query's cache?

My current workaround is to use requestPolicy: 'cache-and-network' and discard the stale value if it's undefined.
But, I'd prefer it if I could essentially reset the state of the query, so it knows that it needs to do a network call again.

Many thanks 🙂

[myieye]

I was not understanding things correctly. What was actually happening is that

• cache.invalidate() was causing my query store to update
• When it updated it got null from the server and excplicitly cached that

So, what I actually needed to fix this was either:

• pause() the queryStore, because I know it will return null and I don't want that to get cached OR
• Add a query update to the cacheExchange that invalidates nulls as they arrive

I ended up doing both for now.