ruby-grape / grape / 42519925321

100%

push

github

Add API.eager_load! to compile an API and load its I18n translations (#3019)

I18n reads its locale files on the first lookup, so in an app that
precompiles its API the first error a process answered still paid for the
load: 3.65 ms against 0.87 ms once the translations were in memory.
API.eager_load! compiles the API and loads the translations, so an app
calling it at boot pays for both there.

It is an explicit call rather than a setting read whenever an API is
compiled, because compile! also runs lazily on the first request: tied to
it, the load would land on that request, even a successful one. compile!
and request handling are unchanged. Rails already loads I18n at boot when
config.eager_load is on; calling an API's eager_load! from Rails is left
to a separate change.

A Simple backend is loaded with translations(do_init: true), the load its
first lookup would run, rather than eager_load!: that one also flags the
backend so every later I18n.reload! loads at once, and raises on a
LazyLoadable backend set to lazy_load. Loading only Grape's own locale
file would not help, as the first lookup still reads the whole load path,
Grape's file included. Any other backend is eager-loaded when it answers
eager_load!, and left to its first lookup otherwise.

Like compile!, eager_load! is kept off the setup steps an API records, so
mounting the API does not run it again.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

1529 of 1529 branches covered (100.0%)

Branch coverage included in aggregate %.

9 of 9 new or added lines in 2 files covered. (100.0%)

4568 of 4568 relevant lines covered (100.0%)

19349.77 hits per line