Skip to content

Encapsulate the RequestProxy use cases #1784

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 25, 2019

Conversation

jtgeibel
Copy link
Member

The RequestProxy value is constructed 3 places, overwriting 1 of 2
values. The fields are made private and 2 new constructors give each
use case a name.

The RequestProxy value is constructed 3 places, overwriting 1 of 2
values.  The fields are made private and 2 new constructors give each
use case a name.
Copy link
Contributor

@smarnach smarnach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is looking good to me. You could add documentation to the constructors or maybe even add unit tests to the file itself, but given how simple the RequestProxy object is I don't think this is strictly necessary.

@jtgeibel
Copy link
Member Author

I've added some docs to the extracted logic. Thanks @smarnach!

@bors r+

@bors
Copy link
Contributor

bors commented Jul 25, 2019

📌 Commit 5baa165 has been approved by jtgeibel

@bors
Copy link
Contributor

bors commented Jul 25, 2019

⌛ Testing commit 5baa165 with merge 25b52da...

bors added a commit that referenced this pull request Jul 25, 2019
Encapsulate the RequestProxy use cases

The RequestProxy value is constructed 3 places, overwriting 1 of 2
values.  The fields are made private and 2 new constructors give each
use case a name.
@bors
Copy link
Contributor

bors commented Jul 25, 2019

☀️ Test successful - checks-travis
Approved by: jtgeibel
Pushing 25b52da to master...

@bors bors merged commit 5baa165 into rust-lang:master Jul 25, 2019
@jtgeibel jtgeibel deleted the encapsulte-requests-proxy branch November 23, 2019 05:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants