feat(response): Add get_header method #518
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
Previously there was no way to check if a header had been set on a response, without accessing _headers which doesn't feel clean. This commit adds a get_header method on the response object for checking if a header is set.
|
👍 LGTM |
| argument of :py:meth:`set_header`. | ||
|
|
||
| Returns: | ||
| The raw value of the header if it is set, or ``None`` |
|
@lwcolton Just a few nits. Could you also rebase on the latest master? Thanks! |
|
@lwcolton Just following up to see if you had a chance to review my comments? |
|
Rebased in #566 |
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.
Previously there was no way to check if a header had been set on
a response, without accessing _headers which doesn't feel clean.
This commit adds a get_header method on the response object for
checking if a header is set.