ruby-grape / grape / 35998836533

100%

master: 100%

Pull #3007

github

Reserve blank? and present? for outside input

`blank?` answers loosely -- nil, false, an empty collection and a
whitespace-only String all count as blank. That is what request data
and values a developer hands over need, as their type is not known.
Grape's own values do have a known type, and `blank?` hid it: whether
nil was possible, whether the collection could be empty, or that the
value was a Class, for which `present?` costs a `respond_to?` miss.

Those sites now ask exactly what the value can be:

- `empty?` for a collection that is never nil: the filter and
  validation stacks, `stacked` results, `**route_options`, the renamed
  params table, the params a `given` dependency filtered
- `nil? || empty?` where nil is a real state: versions, a scope's own
  setting store, the middleware's headers, a route's path input
- truthiness for an object or nil: the entity class, a parent scope,
  the named params, route requirements, routing args, the allowed
  methods, a mount path

Behaviour is unchanged: each check is exact for what reaches it.

Every `blank?` and `present?` left is on outside input, so they are the
places to check for scrubbing, as a `blank?` on a raw request String
raises on an invalid byte (#3006). AGENTS.md now states the rule.

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

1490 of 1490 branches covered (100.0%)

Branch coverage included in aggregate %.

29 of 29 new or added lines in 14 files covered. (100.0%)

4326 of 4326 relevant lines covered (100.0%)

29281.85 hits per line