-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Conversation
Codecov Report
@@ 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
Continue to review full report at Codecov.
|
There was a problem hiding this 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 |
There was a problem hiding this comment.
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
).
@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. |
thanks! |
) (cherry picked from commit c422ff3) Co-authored-by: Ben Timby <btimby@gmail.com>
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
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.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.