ruby-grape / grape / 33914091930

97%

master: 99%

Pull #2898

github

Stop eager loading grape/testing

`Grape::Testing` has been documented as opt-in since 3.3 -- README and the
UPGRADING note for that release both say it is "intended for test environments
only and is not loaded by default" -- but nothing ever excluded it from the
eager load, so `require 'grape'` installed it in every process, production
included.

The two are simply out of order: `loader.eager_load` arrived with Zeitwerk in
2c79b2f9 (2024), and grape/testing.rb was added later in ba7386a8 without being
added to the exclusion list that already held the railtie. The released 3.3.5
gem excludes only `railtie`, so the module has never actually been opt-in.

Excluding it makes the documented behaviour the real one: `require 'grape'`
leaves `Grape::Endpoint` without `before_each` / `reset_before_each` and without
the `Grape::Endpoint#run` wrapper the module prepends. Zeitwerk still registers
the autoload, so referencing the `Grape::Testing` constant loads it as before,
and `require 'grape/testing'` -- what README and UPGRADING have asked for since
3.3 -- is unaffected. spec/grape/testing_spec.rb already requires it and needed
no change.

UPGRADING carries a note under 4.0.0, because an application that never read
the 3.3 one can still be relying on the accident.

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

1244 of 1338 branches covered (92.97%)

Branch coverage included in aggregate %.

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

3947 of 4016 relevant lines covered (98.28%)

26966.14 hits per line