azcore fix: POST responses can be any type#3721
Merged
Merged
Conversation
Contributor
Does the PR have any schema changes?Looking good! No breaking changes found. |
thomas11
force-pushed
the
tkappler/post-primitive-response
branch
from
24c0dd1 to
6613d8f
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3721 +/- ##
=======================================
Coverage 56.40% 56.41%
=======================================
Files 74 74
Lines 11811 11813 +2
=======================================
+ Hits 6662 6664 +2
Misses 4652 4652
Partials 497 497 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
Contributor
|
This PR has been shipped in release v2.73.1. |
This was referenced Sep 1, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3716. In the autorest client, POST responses were unmarshaled into
any, which allows for primitive types as well as objects. In the new azcore client, they were unmarshaled intomap[string]any, requiring the response to be an object.