fix(event_handler): omit Content-Type header from OpenAPI - #8374
Conversation
|
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #8374 +/- ##
========================================
Coverage 96.64% 96.64%
========================================
Files 296 296
Lines 14764 14765 +1
Branches 1245 1245
========================================
+ Hits 14268 14269 +1
Misses 361 361
Partials 135 135 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
leandrodamascena
left a comment
There was a problem hiding this comment.
Thanks for working on this @DebadityaHait
|
Tick the box to add this pull request to the merge queue (same as
|
|
Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience! |
|
Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience! |



Issue number: Fixes #8347
Summary
Changes
User experience
Before, a route that used Body(media_type=application/json-patch+json) and a Literal[...] Content-Type header emitted both the correct request-body media type and a redundant in: header content-type parameter.
After, the request-body media type remains in requestBody.content, content-type is omitted from the generated parameter list, and runtime validation still returns 422 for an incorrect media type.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.