Content type for error response #41
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mbleigh
pushed a commit
that referenced
this pull request
Jul 15, 2011
Content type for error response
mbleigh
pushed a commit
that referenced
this pull request
Dec 5, 2011
Content type for error response
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I just found the 'Content-Type' header for error response is always 'text/html', no matter you set error_format to :txt or :json, as demostrate by line 295-306 in spec/grape/api_spec.rb.
The commit also includes a little refactoring of format handling - duplicated codes are moved into Grape::Middleware::Base::Formats module.