Fix float comparison in duration encode mockapi for query and header params

[Copilot]

Float-typed duration values transmitted as query/header params were compared as strings, causing valid representations like "35625.0" to fail against expected "35625" even though they're numerically equal.

Changes

• New createQueryFloatServerTests helper: Uses parseFloat() for numeric comparison instead of string equality for float query param scenarios
• New createHeaderFloatServerTests helper: Same numeric comparison approach for float header scenarios
• Updated 8 scenarios to use the new float helpers — the ones where whole-number float values create representation ambiguity:
  • floatMilliseconds / float64Milliseconds (35625)
  • floatSecondsLargerUnit (150)
  • floatMillisecondsLargerUnit (210000)

Non-float scenarios (int32, iso8601) and non-ambiguous floats like 35.625 are unchanged — their string comparison remains appropriate.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Bug]: mockapi in e2e test, logic to compare float is not correct</issue_title>
<issue_description>### Describe the bug

mockapi in test https://github.com/microsoft/typespec/blob/main/packages/http-specs/specs/encode/duration/mockapi.ts

On test of duration as float, in query param and header param, it compares with e.g. 35625, which fails other same float value of 35625.0 etc.

Please fix these mockapi, to make it compare the float number (not its string representation).

Reproduction

run test with e.g. 35625.0 as input

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Bug]: mockapi in e2e test, logic to compare float is not correct #9944

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/http-specs@9945

commit: 1b5d62c

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension