ruby-grape / grape / 25564552185 / 5

97%

master: 97%

push

github

Fix README typos, remove obsolete Fixnum section, and clarify optional + values (#2700)

Spelling and grammar:
- "given on an `configuration`" → "based on a `configuration`"
- "Accept` head" → "Accept` header"
- "won't affects" → "won't affect"
- "with' blocks" → "with` blocks" (mismatched quote)
- `required :beer` / `:wine` / `:blah` → `requires` (the DSL method
  is `requires`; the samples as written would raise NoMethodError)
- "the the [grape-entity]" → "the [grape-entity]"

Accuracy:
- §"Accept-Version Header": the strict-mode sentence said the 406 was
  raised when no correct `Accept` header was supplied; the middleware
  checks `HTTP_ACCEPT_VERSION`, so corrected to "Accept-Version".
- "Rack::Etag" → "Rack::ETag" (correct class name).
- Removed the "Integer/Fixnum and Coercions" section comparing Ruby
  2.4 vs. earlier — `grape.gemspec` requires Ruby >= 3.2, where
  `Fixnum` no longer exists.

Replaces an incorrect note about `requires + values + allow_blank`
(closes #2631) with a correct note covering `optional + values`. The
deleted note claimed `:allow_blank` defaults to `true` and that
absence of `:allow_blank` does not prevent `:state` from receiving
blank values — both wrong: `@allow_blank` defaults to `nil`, and
`requires` already rejects `nil` via the values validator. The real
quirk is `optional + values`: `ValuesValidator#validate_param!`
short-circuits on `nil` whenever the param is optional at the root
scope, so missing/`nil`/`""`-coerced-to-`nil` all pass. The new note
documents that and shows `allow_blank: false` as the way to opt out
while still allowing the key to be absent.

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

1055 of 1165 branches covered (90.56%)

Branch coverage included in aggregate %.

3364 of 3457 relevant lines covered (97.31%)

1008.59 hits per line