ruby-grape / grape / 24694315106

97%

master: 97%

Pull #2688

github

Consolidate rescue handler lookup in Middleware::Error

`rescue_handler_for_base_only_class` and `rescue_handler_for_class_or_its_ancestor`
were structurally identical — same option-hash lookup, same fallback to
`default_rescue_handler`. Only the option key and match predicate differed:
`:base_only_rescue_handlers` + `klass == err` for `rescue_from FooError,
rescue_subclasses: false`, versus `:rescue_handlers` + `klass <= err` for the
default exact-or-ancestor form.

Collapse both into `registered_rescue_handler`, which encapsulates the DSL
concept (any handler the user registered via `rescue_from`) and preserves
exact-before-ancestor precedence. A shared `rescue_handler_from(key, &matcher)`
primitive holds the lookup scaffolding once.

`find_handler` now reads as a priority list of four named concepts: user-
registered handler, Grape exception, catch-all, or re-raise. The exact/ancestor
precedence moves one level down, properly encapsulated inside
`registered_rescue_handler`.

No public API change; behavior is identical.

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

1069 of 1153 branches covered (92.71%)

Branch coverage included in aggregate %.

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

3351 of 3404 relevant lines covered (98.44%)

32231.3 hits per line