ruby-grape / grape / 33924269493

97%

master: 99%

Pull #2904

github

Document and spec route requirements given as a capture type

A route's `requirements` are handed to Mustermann as the capture's constraint.
Given a Regexp that only narrows what the route matches, but a Class or a
Symbol Mustermann knows also registers a converter, so the router extracts an
Integer, a Float, a Symbol, a Date or a Gem::Version rather than a String —
`requirements: { id: Integer }` matches `-?\d+` and hands the endpoint `23`.

Nothing exercised it: `Route#tag_utf8!`'s non-String branch had no coverage,
and the README documents `requirements` with regular expressions only, so a
working capability looked like dead code.

Specs at all three levels — the pattern converting and constraining, the
route keeping the converted value out of `params_for` (with the UTF-8 tagging
of a String capture pinned next to it), and an API handing it to the endpoint,
including a `params` block coercing it back, since validation runs after the
router.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

1246 of 1339 branches covered (93.05%)

Branch coverage included in aggregate %.

3962 of 4030 relevant lines covered (98.31%)

27088.75 hits per line