Fix for #3414 - C# generated client using FormUrlEncodedContent instead of StringContent #5029
Conversation
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
…uid templates - ConsumesOnlyFormUrlEncoded will be set to false if json is accepted
Contributor
Author
|
@RicoSuter anything I can do to help with this PR? without this, NSwag generates invalid clients |
Owner
|
Thanks for the PR. |
This was referenced Nov 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This is a fix for #3414. When "x-www-form-urlencoded" is accepted, NSwag will generate an invalid client that sends url encoded form as "application/json". This change checks if "application/json" is accepted and will prioritize it.