Skip to content
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

Allow caller to control HTTP status when using FileResponse #4107

Merged
merged 6 commits into from
Sep 27, 2019

Conversation

btimby
Copy link
Contributor

@btimby btimby commented Sep 26, 2019

What do these changes do?

Allow caller to control HTTP status when using FileResponse

Are there changes in behavior for the user?

None

Related issue number

#4106

Checklist

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • If you provide code modification, please add yourself to CONTRIBUTORS.txt
    • The format is <Name> <Surname>.
    • Please keep alphabetical order, the file is sorted by names.
  • Add a new news fragment into the CHANGES folder
    • name it <issue_id>.<type> for example (588.bugfix)
    • if you don't have an issue_id change it to the pr id after creating the pr
    • ensure type is one of the following:
      • .feature: Signifying a new feature.
      • .bugfix: Signifying a bug fix.
      • .doc: Signifying a documentation improvement.
      • .removal: Signifying a deprecation or removal of public API.
      • .misc: A ticket has been closed, but it is not of interest to users.
    • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

@psf-chronographer psf-chronographer bot added the bot:chronographer:provided There is a change note present in this PR label Sep 26, 2019
@codecov-io
Copy link

codecov-io commented Sep 26, 2019

Codecov Report

Merging #4107 into master will decrease coverage by 0.04%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4107      +/-   ##
==========================================
- Coverage   97.86%   97.81%   -0.05%     
==========================================
  Files          43       43              
  Lines        8807     8807              
  Branches     1378     1378              
==========================================
- Hits         8619     8615       -4     
- Misses         75       78       +3     
- Partials      113      114       +1
Impacted Files Coverage Δ
aiohttp/web_fileresponse.py 96.59% <100%> (-1.14%) ⬇️
aiohttp/connector.py 96.93% <0%> (-0.33%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dd9db9a...2c6478c. Read the comment docs.

Copy link
Member

@asvetlov asvetlov left a comment

Choose a reason for hiding this comment

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

LGTM.
Good catch!

CONTRIBUTORS.txt Outdated
@@ -275,3 +275,4 @@ Yury Selivanov
Yusuke Tsutsumi
Марк Коренберг
Семён Марьясин
Ben Timby
Copy link
Member

Choose a reason for hiding this comment

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

The file is supposed to keep alphabetical order.
Please move this line to appropriate place (or just run sort CONTRIBUTORS.txt -o CONTRIBUTORS.txt).

@webknjaz
Copy link
Member

@btimby pro tip: avoid using master branch in your fork, it'll create you a lot of problems. better create a new branch before starting each PR.

@asvetlov asvetlov merged commit c422ff3 into aio-libs:master Sep 27, 2019
@asvetlov
Copy link
Member

thanks!

asvetlov pushed a commit that referenced this pull request Sep 27, 2019
)

(cherry picked from commit c422ff3)

Co-authored-by: Ben Timby <btimby@gmail.com>
asvetlov added a commit that referenced this pull request Sep 27, 2019
) (#4113)

(cherry picked from commit c422ff3)

Co-authored-by: Ben Timby <btimby@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot:chronographer:provided There is a change note present in this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants