Fix Parameter name mix-up in HttpResponse#19
Merged
bonesoul merged 1 commit intobonesoul:masterfrom Apr 23, 2019
hisleiterj:master
Merged
Fix Parameter name mix-up in HttpResponse#19bonesoul merged 1 commit intobonesoul:masterfrom hisleiterj:master
bonesoul merged 1 commit intobonesoul:masterfrom
hisleiterj:master
Conversation
…closeConnection")
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
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.
The parameter closeConnection in different ctor overloads of HttpResponse should be named keepAliveConnection instead: It gets negated when stored in private field _closeConnection (c.f. line 188).
Strictly speaking, this PR introduces a breaking change (for callers who use named arguments). However, it should not effect many consumers. The alternative to keep the name of the parameter but change its behavior accordingly would be less compatible for existing code bases.