ruby-grape / grape
99%
master: 99%

Repo Added 04 Apr 2013 06:08AM UTC

Committed 17 Sep 2026 09:06PM UTC coverage: 99.042% (-0.005%) from 99.047%

Committed by

Commit Message

Collapse the lazy configuration value tree into one path-based Value

A remountable API reads `configuration` while its own class body runs,
long before anybody mounts it and supplies one, so the read has to be
recorded and replayed once per mount.

To remember what had been read, `Grape::Util::Lazy` eagerly mirrored the
whole `with:` Hash as a tree of wrapper objects, and `[]` mutated the
child it returned, stamping it with the path it was reached by before
handing back that shared node. Reading was writing, and it was only safe
because every read re-stamped the path.

The tree carried its own weight in oddities: `@value_hash` held an Array
in `ValueArray`, `@value` was dead in both enumerables (`super` set it,
both override `evaluate`), and the whole structure existed so that
`evaluate` could answer a deep `HashWithIndifferentAccess` - which is
what `Hash#with_indifferent_access` already answers, identically, down to
the classes at every depth.

A read is now one immutable `Lazy::Value` holding the configuration and
the path of keys walked into it. `[]` answers a fresh Value one key
deeper, `evaluate` walks the path, and `evaluate_from` walks that same
path through the configuration a mount supplied. `ValueHash`,
`ValueArray` and `ValueEnumerable` are deleted, and
`EndpointConfiguration` carries the single conversion.

This fixes nested configuration reads. `configuration[:db][:host]`
raised `NoMethodError` while the class body ran, because a key missing
from a base instance's empty configuration yielded a plain `Value`,
which had no `[]`. Reading a key nested in a Hash or an Array was
impossible in a remountable API.

Building a configuration is 1.5x faster, and `evaluate` - which runs per
request through `configuration` inside an endpoint - is 13x faster
(1.79 us to 136 ns).

The old specs asserted which wrapper class `[]` answered, so they are
replaced by specs on what a read answers. Two properties the tree
provided incidentally are now pinned: ... (continued)

Coverage Stats

1424 of 1479 branches covered (96.28%)

Branch coverage included in aggregate %.

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

4260 of 4260 relevant lines covered (100.0%)

28365.88 hits per line

4260 RELEVANT LINES 4260 COVERED LINES

28365.88 HITS PER LINE

Builds	Branch	Commit	Type	Ran	Committer	Via	Coverage
35274783394	collapse-lazy-value-tree	Collapse the lazy configuration value tree into one path-based Value A remountable API reads `configuration` while its own class body runs, long before anybody mounts it and supplies one, so the read has to be recorded and replayed once per mount...	Pull #2950	17 Sep 2026 09:06PM UTC	ericproulx	github	99.04
35274722362	collapse-lazy-value-tree	Collapse the lazy configuration value tree into one path-based Value A remountable API reads `configuration` while its own class body runs, long before anybody mounts it and supplies one, so the read has to be recorded and replayed once per mount...	push	17 Sep 2026 09:06PM UTC	ericproulx	github	99.04

ruby-grape / grape
99%
master: 99%

ruby-grape / grape 99% master: 99%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

CHANGE BRANCH x

Relevant lines Covered

Source Files on collapse-lazy-value-tree

Recent builds

ruby-grape / grape
99%
master: 99%

README BADGES
x

CHANGE BRANCH
x