Skip to content

Fix getFunctionLogs orderBy parameter with proper enum validation#67

Merged
binggg merged 1 commit intomainfrom
claude/issue-64-20250710_150520
Jul 10, 2025
Merged

Fix getFunctionLogs orderBy parameter with proper enum validation#67
binggg merged 1 commit intomainfrom
claude/issue-64-20250710_150520

Conversation

@binggg
Copy link
Copy Markdown
Member

@binggg binggg commented Jul 10, 2025

Fix getFunctionLogs orderBy parameter with proper enum validation

  • Update TypeScript implementation to use enum validation for order and orderBy fields
  • Add enum constraints to JSON schema for type safety
  • orderBy now only accepts: function_name, duration, mem_usage, start_time
  • order now only accepts: desc, asc
  • Enhanced field descriptions with explanations
  • Prevents API errors like "OrderBy取值与规范不符" when using invalid values like "RequestTime"

Fixes #64

🤖 Generated with Claude Code

- Update TypeScript implementation to use enum validation for order and orderBy fields
- Add enum constraints to JSON schema for type safety
- orderBy now only accepts: function_name, duration, mem_usage, start_time
- order now only accepts: desc, asc
- Enhanced field descriptions with explanations
- Prevents API errors like "OrderBy取值与规范不符" when using invalid values like "RequestTime"

Fixes #64

Co-authored-by: Booker Zhao <binggg@users.noreply.github.com>
@binggg binggg merged commit e0036d6 into main Jul 10, 2025
2 checks passed
binggg added a commit that referenced this pull request Sep 4, 2025
…_150520

Fix getFunctionLogs orderBy parameter with proper enum validation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MCP工具错误: getFunctionLogs

1 participant