Remove JSON exposition format support #18
Merged
Conversation
This file contains 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
grobie
force-pushed
the
remove-json-format
branch
from
df2c76f
to
564f807
Compare
|
The tests seem to be failing, otherwise 👍 |
|
👍 for removing it On Tue, Jan 12, 2016, 9:42 AM Brian Brazil notifications@github.com wrote:
|
|
@brian-brazil Yeah, unfortunately they broke the |
JSON has been deprecated as exposition format long time ago. Time to remove support from client_ruby.
grobie
force-pushed
the
remove-json-format
branch
from
564f807
to
c81b438
Compare
|
Tests are green. Travis issues -.- |
grobie
added a commit
that referenced
this pull request
Jan 12, 2016
Remove JSON exposition format support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
JSON has been deprecated as exposition format long time ago. Time to
remove support from client_ruby.
@brian-brazil @fabxc