feat(api-body): add support for encoding in ApiBody decorator#3699
Merged
kamilmysliwiec merged 3 commits intonestjs:masterfrom Apr 15, 2026
Merged
Conversation
…ate SwaggerExplorer to handle encoding in request body
micalevisk
approved these changes
Feb 1, 2026
Contributor
Author
|
aww... I was hoping this to get merged with today's release! 😞 Is there anything else I can do to get this merged soon @micalevisk and @kamilmysliwiec ? |
…-form-data-encoding
1 task
…-form-data-encoding
Contributor
Author
|
@kamilmysliwiec I have aligned my PR to the latest release |
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.
feat(api-body): add support for encoding in ApiBody decorator and update SwaggerExplorer to handle encoding in request body
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: 3698
What is the new behavior?
Does this PR introduce a breaking change?
Other information