Add toString and toXContent to IndexResponse #3871
Closed
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
|
+1! |
|
Looks good, but should we do this consistently for all response classes? (moving ToXContent from rest code to response classes and implement toString). Like: UpdateResponse, DeleteResponse, SearchResponse, ExplainResponse, DeleteByQueryResponse etc? |
|
I completely agree - I will look into this soon hopefully |
clintongormley
added
v2.0.0-beta1
>enhancement
:Core/Infra/Transport API
|
closing for now this didn't go anywhere |
s1monw
removed
:Core/Infra/Transport API
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.
Currently
IndexResponsedoes not like other responses implementToXContentand neither atoStringmethod. We should try to be consistent here.