ruby-grape / grape / 27497052435 / 22

97%

master: 97%

Pull #2764

github

Route Grape::Json through the non-deprecated MultiJSON API

multi_json 1.21.0 deprecated the `MultiJson` constant (in favor of
`MultiJSON`) and `MultiJSON.dump` (in favor of `generate`), removed in
2.0. Grape detected the backend via `::MultiJson` and called `dump`, so
users on multi_json >= 1.21 saw deprecation warnings (#2763).

Detect `::MultiJSON` and give `Grape::Json` a small facade whose `dump`
delegates to `MultiJSON.generate` (byte-identical output), re-exposing
`parse` since the facade no longer inherits MultiJSON's methods. Behavior
is unchanged; the stdlib fallback is untouched.

Following #2762 (Grape standardizes on `parse`, never `load`, for JSON),
the two remaining `Grape::Json.load` spec helpers move to `parse`, so
`Grape::Json.load` no longer appears anywhere and the facade needs no
`load`.

Also give the legacy multi_json (< 1.21) branch the same facade treatment
mapping dump/parse onto the dump/load it exposes — it has no generate/parse,
so `Grape::Json.parse` would otherwise raise NoMethodError there.

Cover both backends in CI: pin gemfiles/multi_json.gemfile to >= 1.21 and
add gemfiles/multi_json_1_20.gemfile (< 1.21), each running the
spec/integration/multi_json suite. The integration spec keys off the
`MultiJson` constant (defined on both lines) and drives a real Grape API
through the parser and JSON formatter.

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

41 of 1219 branches covered (3.36%)

Branch coverage included in aggregate %.

1758 of 3637 relevant lines covered (48.34%)

0.67 hits per line