-
Notifications
You must be signed in to change notification settings - Fork 420
fix(event_handler): apply serialization as the last operation for middlewares #3392
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## develop #3392 +/- ##
========================================
Coverage 95.39% 95.39%
========================================
Files 208 208
Lines 9637 9638 +1
Branches 1766 1766
========================================
+ Hits 9193 9194 +1
Misses 330 330
Partials 114 114 ☔ View full report in Codecov by Sentry. |
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.
pending CI checks
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.
tiny change to prevent a possible hyrum law case of an unknown internal dependency
Kudos, SonarCloud Quality Gate passed!
|
Issue number: #3391
Summary
Changes
This PR moves the serialization on event handler to the very last step before returning to the client. This allows all middlewares to see the original returns from the handler.
The serialization is also only applied if the content type of the response is JSON. This means we don't try to apply the serialization to HTML or PLAIN responses.
User experience
After this PR, a user can again use a custom serializer, even when using data validation.
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.