-
Notifications
You must be signed in to change notification settings - Fork 208
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
application/x-www-form-urlencoded request content type is not handled properly #219
Closed
Tracked by
#1049
Labels
enhancement
New feature or request
fixed
generator
Issues or improvements relater to generation capabilities.
Milestone
Comments
baywet
added a commit
that referenced
this issue
Jun 7, 2021
4 tasks
baywet
added
the
generator
Issues or improvements relater to generation capabilities.
label
Jul 21, 2021
when implemented, we should clear the appsettings.json to be able to ship self-contained executable |
Example in OpenAPI specification for request body that is form-urlencoded https://spec.openapis.org/oas/v3.1.0#support-for-x-www-form-urlencoded-request-bodies |
meeting notes:
stand-up new packages for:
Create the issues for the other languages |
This was referenced Dec 14, 2022
Merged
Repository owner
moved this from In Progress
to Done
in Kiota
Dec 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
fixed
generator
Issues or improvements relater to generation capabilities.
If the type generation seems to be working properly for this request content type, the content serialization won't as we don't have a serializer for it. Adding a serializer should be trivial using the natively available libraries on the platform to build the body so encoding is handled for us.
More reading
originally reported
AB#9787
The text was updated successfully, but these errors were encountered: