Bug: API接口获取统计数据失败

[g1331]

实际请求：

curl --location --request POST 'https://host/api/actions/statistics/getUserStatistics' \
--header 'User-Agent: Apifox/1.0.0 (https://apifox.com)' \
--header 'Content-Type: application/json' \
--header 'Cookie: auth-token=token; auth-token=token' \
--header 'Accept: */*' \
--header 'Host: host' \
--header 'Connection: keep-alive' \
--data-raw '{
  "timeRange": "hour",
  "userId": 1
}'

log:

{"level":"error","time":"2025-11-28T10:02:50.913Z","pid":1,"hostname":"b907c16eacd1","err":{"type":"Error","message":"Invalid time range: [object Object]","stack":"Error: Invalid time range: [object Object]\n    at n (/app/.next/server/app/api/actions/[...route]/route.js:75:7423)\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async r (/app/.next/server/app/api/actions/[...route]/route.js:121:27522)\n    at async g (/app/.next/server/chunks/5832.js:1:5222)\n    at async /app/.next/server/app/api/actions/[...route]/route.js:121:71048\n    at async b (/app/.next/server/app/api/actions/[...route]/route.js:121:72082)\n    at async g (/app/.next/server/chunks/5832.js:1:5222)\n    at async /app/.next/server/chunks/5832.js:1:12729\n    at async rN.do (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:5:21042)\n    at async rN.handle (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:5:25860)"},"msg":"Failed to get user statistics:"}
{"level":"warn","time":"2025-11-28T10:02:50.913Z","pid":1,"hostname":"b907c16eacd1","error":"获取统计数据失败：Invalid time range: [object Object]","msg":"[ActionAPI] statistics.getUserStatistics failed:"}

版本v0.3.15

[ding113]

@claude fix it

[ding113]

问题分析

经过调查，我发现了问题的根本原因：

错误日志显示: Invalid time range: [object Object]

这说明 timeRange 参数接收到的是一个对象而不是预期的字符串。

根本原因

在 src/lib/api/action-adapter-openapi.ts 中，createActionRoute 函数调用 Server Action 时：

const rawResult = await action(body);  // body = { timeRange: "hour", userId: 1 }

它把整个请求体对象作为单一参数传递给了 getUserStatistics 函数，但该函数的签名是：

export async function getUserStatistics(
  timeRange: TimeRange = DEFAULT_TIME_RANGE
): Promise<ActionResult<UserStatisticsData>>

所以 timeRange 参数实际接收到的是 { timeRange: "hour", userId: 1 }，而不是 "hour" 字符串。

修复方案

我已提交 PR #232 来修复此问题。修复内容：

• 根据 schema 的 keys 从请求体中提取参数
• 将参数作为位置参数（positional arguments）传递给 action 函数
• 单参数 action 现在会接收到正确的值，而不是包装对象

PR 链接

#232

🤖 Response from Claude AI

[g1331]

v0.3.19仍然存在问题：

请求 URL:

POSThttps://xxx.com/api/actions/statistics/getUserStatistics

Header:

名称 | 值 -- | -- User-Agent | Apifox/1.0.0 (https://apifox.com) Content-Type | application/json Cookie | auth-token={{token}} Accept | */* Host | xxx.com Accept-Encoding | gzip, deflate, br Connection | keep-alive Content-Length | 43

Body:

Body 类型 : application/json

{
  "timeRange": "hour",
  "userId": 1
}

log:

{"level":"error","time":"2025-12-01T02:02:18.420Z","pid":1,"hostname":"d2954058217c","err":{"type":"Error","message":"Invalid time range: [object Object]","stack":"Error: Invalid time range: [object Object]\n    at n (/app/.next/server/app/api/actions/[...route]/route.js:75:7423)\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async r (/app/.next/server/app/api/actions/[...route]/route.js:121:20090)\n    at async g (/app/.next/server/chunks/5832.js:1:5222)\n    at async /app/.next/server/app/api/actions/[...route]/route.js:121:71175\n    at async b (/app/.next/server/app/api/actions/[...route]/route.js:121:72209)\n    at async g (/app/.next/server/chunks/5832.js:1:5222)\n    at async /app/.next/server/chunks/5832.js:1:12729\n    at async rN.do (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:5:21042)\n    at async rN.handle (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:5:25860)"},"msg":"Failed to get user statistics:"}
{"level":"warn","time":"2025-12-01T02:02:18.421Z","pid":1,"hostname":"d2954058217c","error":"获取统计数据失败：Invalid time range: [object Object]","msg":"[ActionAPI] statistics.getUserStatistics failed:"}

[github-actions]

This issue has been automatically marked as stale because it has not had any activity in the last 30 days.

If this issue is still relevant:

• Please comment to keep it open
• Add any new information that might help resolve it

This issue will be automatically closed in 14 days if there is no further activity.