ruby-grape / grape / 28782340033 / 2

97%

master: 97%

Pull #2786

github

Make requirements and anchor first-class endpoint inputs

`route`'s documented options `requirements:` and `anchor:` are now explicit
keyword arguments rather than opaque keys in the `route_options` bag, with
`**route_options` still catching any custom options. They travel as their
own endpoint inputs (`Grape::Endpoint::Options` gains `:requirements` and
`:anchor` members; `Grape::Endpoint.new` gains matching keywords) and
`to_routes` reads them via `config.requirements` / `config.anchor` instead
of `route_options[...]`. The verb methods forward `**options` unchanged, so
`get(':id', requirements: {...}, anchor: false)` still works.

Like `params`, they no longer appear in `route.options`; the effective value
comes from the `route.requirements` / `route.anchor` readers. Mounts pass
`anchor: false` as a keyword too.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

1103 of 1222 branches covered (90.26%)

Branch coverage included in aggregate %.

3548 of 3662 relevant lines covered (96.89%)

974.86 hits per line