MutationKey and QueryKey consistency?

[bzbetty]

Was looking at doing automated query validation based on query/mutation key (https://tkdodo.eu/blog/automatic-query-invalidation-after-mutations) which is like a 2 line change in the mutation cache.

However I noticed that the mutation key and query key seem to use very different formats for the url

export const getTagsQueryKey = (workspaceId: GetTagsPathParams['workspaceId']) =>
  [{ url: '/workspaces/:workspaceId/tags', params: { workspaceId: workspaceId } }] as const

export const createTagMutationKey = () => [{ url: '/workspaces/{workspaceId}/tags' }] as const

Is there a reason for this that I'm missing?

[stijnvanhulle]

@bzbetty when using useQuery you are passing your params to the hook, but with useMutation, you need to call mutate(params) instead(no use of hook props). This means we cannot save the params to the mutationKey as we don't have access to it when using useMutation.

[bzbetty]

@stijnvanhulle right, but is there any reason for the {} formatting vs the : formatting?

eg why use '/workspaces/:workspaceId/tags' vs '/workspaces/{workspaceId}/tags'

[stijnvanhulle]

@bzbetty Hmm this is weird, let me adjust to use the same format('/workspaces/:workspaceId/tags' )