Remote Functions: Keyed Refresh

Describe the problem

With remote functions it's possible to force a refresh of a query in a command by running the refresh action on the query eg getLikes(id).refresh() which is fine when you know the parameters of the other queries; but if you are using multiple of the same query, or a query with multiple parameters that you don't have access to then running the refresh is difficult.

Describe the proposed solution

Tanstack has a good approach where keys are defined on the query, then it's possible to invalidate all queries with a matching key eg:

const todoListQuery = useQuery({
  queryKey: ['todos'],
  queryFn: fetchTodoList,
})
const todoListQuery = useQuery({
  queryKey: ['todos', { page: 1 }],
  queryFn: fetchTodoList,
})

queryClient.invalidateQueries({ queryKey: ['todos'] })

A configuration could be added to the remote function query:

export const getToDos = query(
    z.number(),
    async(page) => {
        fetchPagedTodos(page)
    },
    {
          queryKey: (page) => ["todo", page] 
     }

)

  export const updateTodo = command(
      z.string(),
      async (id) => {
          await updateTodo(id);
          invalidateQueries([
              ["todo"],           
              ["user", "stats"]
          ])
      }
  )

Alternatives considered

No response

Importance

would make my life easier

Additional Information

No response

Start by tracing how remote function queries expose their refresh action and how commands currently trigger refreshes. Compare that behavior with the proposed queryKey and invalidateQueries examples, then determine the matching-key semantics and API shape. Done means related remote function queries can be invalidated without knowing every query parameter.