-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Avoid calling response prepare hook if its empty #9173
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #9173 +/- ##
=======================================
Coverage 98.31% 98.31%
=======================================
Files 107 107
Lines 34483 34484 +1
Branches 4093 4094 +1
=======================================
+ Hits 33901 33902 +1
Misses 411 411
Partials 171 171
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Backport to 3.10: 💚 backport PR created✅ Backport PR branch: Backported as #9188 🤖 @patchback |
(cherry picked from commit d3c3c6a)
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #9189 🤖 @patchback |
(cherry picked from commit d3c3c6a)
…k if its empty (#9188) Co-authored-by: J. Nick Koston <[email protected]>
…k if its empty (#9189) Co-authored-by: J. Nick Koston <[email protected]>
What do these changes do?
Avoid calling response prepare hook if its empty as its likely to be empty in most cases
Are there changes in behavior for the user?
no
Is it a substantial burden for the maintainers to support this?
no
related issue #2779
before
after