Respect content-type from provides
route annotations
#50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Formatter middleware now respects
provides
annotation for routes anduses it both as default and as a restriction on allowed response
content types.
This makes it possible to for ex. output binary blobs on specific paths,
while keeping the rest of the paths as structured data.
To acheive this, we needed to make the following changes:
Raisin::Middleware::Formatter
is now aware of the running Raisin app(via
raisin
attribute)::Formatter->negotiate_format
method has gained a new parmeter toallow for picking the proper default when
provides
is configured andAccept: */*
header is sent