ruby-grape / grape / 41546235719

100%

master: 100%

Pull #3052

github

Add an RFC 9457 problem details error formatter

Grape had no way to answer errors as RFC 9457 problem details:
application/problem+json appeared nowhere in lib/, and an error formatter
could shape the body but not the Content-Type, which always followed the
request format.

Grape::ErrorFormatter::ProblemJson, registered as :problem_json, renders
an about:blank problem whose title is the status phrase and whose detail
is the message. A Hash message brings its own members (type, title,
instance, extensions) over the defaults; status is always the response's,
as the RFC requires. A validation failure lists its parameters in an
errors extension shaped as ValidationErrors#as_json, whether Grape
answered it or a rescue_from handed it to error!.

An error formatter can now name the media type of its errors with
content_type (nil on ErrorFormatter::Base, so nothing else changes), and
Middleware::Error labels the error, its failsafe 500 and error! with it.
A Content-Type the error carries still wins.

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

1531 of 1531 branches covered (100.0%)

Branch coverage included in aggregate %.

40 of 40 new or added lines in 3 files covered. (100.0%)

4564 of 4564 relevant lines covered (100.0%)

30848.38 hits per line