[dinwwwh]

Requested by dinwwwh · project thread

What

This is a test-only change. The literal-text test in router.test.ts now adds /f/{+p}/id} and checks two requests:

• /f/1/id} matches it, with { p: '1' }.
• /f/1/id matches nothing.

Why

Since #186, the tree build calls toSegment only for parts that start with {. A catch-all's tail segments still go through toSegment whatever they start with, and so do parse's callers (createPrefixMatcher and the two-catch-all check in add). Mutation testing found that dropping the leading-{ half of toSegment's param check failed no test, even with the 73 tests now on main. With that mutant, id} becomes a param named d, so /f/1/id matches. The new assertions catch it.

Checks

• All 73 router tests pass, and pnpm check passes.
• With that mutant applied, the test fails.

---

Generated by Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[codspeed]

Merging this PR will not alter performance

1 warning

⚠️ 1 benchmark is dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

✅ 29 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing claude/project-thread-m32ra9 (11b3817) with main (6b348e1)²}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (1e46b22) during the generation of this report, so 6b348e1 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[pullfrog]

✅ No new issues found.

Reviewed changes

• Pin catch-all tail ending in } as literal — adds /f/{+p}/id} to the literal-segment suite plus assertions that /f/1/id} matches ({ p: '1' }) and /f/1/id does not.

I verified the PR's central claim: with the leading-{ half of toSegment's check removed, id} becomes param d and the new assertion fails (params.d = 'id}'). The full router suite passes as-is. Test-only, no production code touched.

  ^{｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}