[vue-query] queryClient.fetchQuery passes getter options through without unwrapping

未关闭
#11,102 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@byungsker 已经在做这个了。

开始于 2026年7月22日。

  • #11103 来自 @byungsker —— 未关闭
  • #11108 来自 @MaNaN1803 —— 已关闭,未合并

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
typescript

调研方向

从 @tanstack/vue-query QueryClient.fetchQuery 的实现及其对 cloneDeepUnref 的调用开始。查看 PR #11103 中链接的针对性回归测试,然后验证 getter 返回的选项对象在到达 query-core 之前会被求值并解包。

由索引模型根据 Issue 内容生成。

描述

Describe the bug

QueryClient.fetchQuery in @tanstack/vue-query has an overload that accepts getter-function options, but the runtime implementation currently passes that top-level function through to query-core instead of evaluating it first.

The overload allows this shape:

queryClient.fetchQuery(() => ({
  queryKey: ["foo", ref("bar")],
  queryFn,
}))

But the implementation calls cloneDeepUnref(options) directly. cloneDeepUnref unwraps refs and nested query-key getters, but it does not call a top-level function value. As a result, query-core receives the function itself instead of the resolved FetchQueryOptions object.

Your minimal, reproducible example

Focused regression test in the linked PR: https://github.com/TanStack/query/pull/11103/files#diff-3d6cc18a7ff7e8e5afb08c0e3cba8d9f3e08fb9c6f6c59f1f5f58dc12f3f8b8e

Minimal code shape:

import { QueryClient } from "@tanstack/vue-query"
import { ref } from "vue"

const queryClient = new QueryClient()
const queryFn = () => Promise.resolve("mock")

queryClient.fetchQuery(() => ({
  queryKey: ["foo", ref("bar")],
  queryFn,
}))
Steps to reproduce
  1. Create a Vue Query QueryClient.
  2. Call queryClient.fetchQuery with a getter function returning FetchQueryOptions.
  3. Observe that the getter is not evaluated before delegating to query-core.

A focused test shows the current behavior clearly:

queryClient.fetchQuery(() => ({
  queryKey: queryKeyRef,
  queryFn: fn,
}))

expect(QueryClientOrigin.prototype.fetchQuery).toHaveBeenCalledWith({
  queryKey: queryKeyUnref,
  queryFn: fn,
})

Currently the received argument is [Function anonymous].

Expected behavior

queryClient.fetchQuery(() => options) should evaluate the top-level getter, then deep-unref the returned options object before passing it to query-core.

How often does this bug happen?

Every time

Screenshots or Videos

No response

Platform
  • OS: macOS
  • Browser: N/A
  • Runtime: Node.js v24.13.0
  • Adapter: vue-query
  • Vue runtimes tested: Vue 2 / Vue 2.7 / Vue 3
Tanstack Query adapter

vue-query

TanStack Query version

v5.101.4 / current main branch at commit 86bb8a6fb

TypeScript version

TypeScript 5.9.3 in the local repo; package type tests also passed across the repo's configured TS 5.4 through TS 6.0 matrix.

Additional context

I could not find an existing open issue or PR for this with these searches:

  • vue queryClient fetchQuery getter options cloneDeepUnref
  • fetchQuery getter function options vue-query
主要语言
TypeScript
星标
50.6k
派生
4.2k
平均合并
9 小时 50 分钟
30 天内合并 PR
310

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TanStack/query 的其他 Issue

查看 TanStack/query 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。