Move test-only search response x-content-parsing code to test codebase#105308
Merged
original-brownbear merged 3 commits intoelastic:mainfrom Feb 9, 2024
original-brownbear:drop-more-response-parsing
Merged
Move test-only search response x-content-parsing code to test codebase#105308original-brownbear merged 3 commits intoelastic:mainfrom original-brownbear:drop-more-response-parsing
original-brownbear merged 3 commits intoelastic:mainfrom
original-brownbear:drop-more-response-parsing
Conversation
Loads of code here that is only used in tests and one duplicate unused class that was only used as an indirection to parsing the `AsyncSearchResponse`. Moved what I could easily move via automated refactoring to `SearchResponseUtils` in tests and removed the duplicate now unused class from the client codebase.
Collaborator
|
Pinging @elastic/es-search (Team:Search) |
mark-vieira
approved these changes
Feb 8, 2024
Contributor
Author
|
Thanks both! |
Contributor
|
Related to #83423 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Mostly motivated by the wish to isolate where search responses are created in prod code as much as possible so that we can confidently clean up the remaining unpooled search response uses:
Loads of code here that is only used in tests and one duplicate unused class that was only used as an indirection to parsing the
AsyncSearchResponse. Moved what I could easily move via automated refactoring toSearchResponseUtilsin tests and removed the duplicate now unused class from the client codebase.