Expose response headers in service result as a Pair #4
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.
In creating #2, we allowed for sending arbitrary headers, such an ETag value for
If-None-Match
, or a value forIdempotency-Key
.This PR provides a way to read headers from the service result. The only way to capture the returned ETag value is to read the response headers, which was impossible prior to this PR.
There's also a small consistency change. Since we're using the
Headers
type in the result for the response, we change the request type to also beHeaders
to match. This changes the call site a bit since the headers should go throughHeadersBuilder
:Or, if sending multiple headers, something like:
On the response side, use destructuring to get at the pair values:
... or, when you don't care about the response headers: