Skip to content

fix: accept whole-number float maxResults values#327

Open
kuishou68 wants to merge 1 commit intodmtrKovalenko:mainfrom
kuishou68:fix/326-maxresults-whole-float
Open

fix: accept whole-number float maxResults values#327
kuishou68 wants to merge 1 commit intodmtrKovalenko:mainfrom
kuishou68:fix/326-maxresults-whole-float

Conversation

@kuishou68
Copy link
Copy Markdown

Closes #326

Summary

  • accept whole-number float values like 30.0 for maxResults
  • keep rejecting fractional values like 30.5
  • add serde regression tests for integer, whole-float, and fractional-float cases

Notes

This is aimed at MCP client interoperability: some wrappers serialize JSON numbers as floats even when the logical value is integral.

Testing

  • not run in this sandbox (cargo/rustc are unavailable here)
  • added focused deserialization tests in crates/fff-mcp/src/server.rs

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: accept whole-number float maxResults values from clients

1 participant