Invalidating Queries on all query keys in group

[Morzaram]

Hey everyone,

Not sure how to title this exactly but I need to invalidate all queryKeys for fetching all conversations

ie

/conversation/1
/conversation/2
/conversation/3

The thing is, when I do this like so

queryClient.invalidateQueries({
        queryKey: [getConversationQueryKey.name],
      });

I expect

return await queryClient.ensureQueryData(
      {
          staleTime: 1000 * 60 * 5,
          ...getConversationOptions({
            path: { id: params.conversation_id },
          }),
        }
    );

to refetch. But it doesn't. am I doing something wrong? Is that not how queryKey construction work within HeyAPI?

Thank you!

[Redmega]

Double check your usage of getConversationQueryKey, I believe that should be a function which returns an array, and not an object with a .name property as you've shown in your example. I don't think it has name at all actually (Unless maybe name comes from the openapi spec and I just don't have them set in my yml).

_id should be consistent between your different getConversationOptions calls, so you can use predicate to invalidate them:

queryClient.invalidateQueries({
  predicate: (query) =>
    query.queryKey[0]._id === getConversationQueryKey()[0]._id // or use the operation id "getConversation" or whatever it happens to be 
})

[Morzaram]

Thanks for the response! This works. For anyone else, here's how I did it based off of Redmega's answer. That being said, it feels a bit dirty accessing private attributes and building this with fake params

queryClient.invalidateQueries({
  predicate: (query) => {
    return [
      voicesQuery.queryKey[0]._id,
      conversationQuery("1").queryKey[0]._id,
    ].includes(query.queryKey[0]._id);
  },
});

Appreciate you taking the time!

[mrlubos]

Thanks for the help (again) @Redmega!

@Morzaram, I could've named it id but chose not to in case it would collide with other plugins or features down the road. I might change it at some point, underscores felt safer, that's all!

The other thing you mentioned, I think there's an issue to make the options optional so you wouldn't have to fake it. For what it's worth, I tend to ignore with @ts-expect-error in the meantime rather than passing fake values