ruby-grape / grape / 33925937310

97%

master: 99%

Pull #2905

github

Nest any lone route_param requirement, and reject a non-Hash elsewhere

`route_param` nested a lone `requirements:` under the param name only when it
was a Regexp. Every other constraint — a capture type such as `Integer` or
`:date` — travelled unwrapped into `Endpoint#prepare_routes_requirements`,
which merges the requirement Hashes of the namespaces a route sits in, and
raised `TypeError: no implicit conversion of Class into Hash` there. That
happens when routes are built, so a mistake in the API's definition surfaced
on the first request, from a method that names neither the route nor the
requirement.

The param is named at the call, so nest any lone constraint, the way the
Regexp shorthand already did. `namespace` and an endpoint have no single param
to attach one to, so they now reject a non-Hash `requirements` where it is
written, with a message that says what was expected.

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

1248 of 1341 branches covered (93.06%)

Branch coverage included in aggregate %.

4 of 4 new or added lines in 1 file covered. (100.0%)

3967 of 4035 relevant lines covered (98.31%)

27105.02 hits per line