You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like the support for other media-types in API specification than application/json. Right now I am using a raw endpoint, but it would be really nice if application/x-www-form-urlencoded would also be supported. Best would be a combination so it's checking both.
How I used to do this before (with echo framework) on certain endpoints - like OAuth token endpoints - would be to annotate request structs with the following:
The logic would be if the content-type is application/x-www-form-urlencoded it would use the form tags. Else if application/json is the content-type it would behave as normal.
Would this be something that is feasable and/or wanted by others?
The text was updated successfully, but these errors were encountered:
srs
changed the title
Porposal: Form url-encoded support API
Porposal: Form url-encoded support in API
Nov 21, 2024
I would like the support for other media-types in API specification than
application/json
. Right now I am using araw
endpoint, but it would be really nice ifapplication/x-www-form-urlencoded
would also be supported. Best would be a combination so it's checking both.How I used to do this before (with echo framework) on certain endpoints - like OAuth token endpoints - would be to annotate request structs with the following:
The logic would be if the content-type is
application/x-www-form-urlencoded
it would use theform
tags. Else ifapplication/json
is the content-type it would behave as normal.Would this be something that is feasable and/or wanted by others?
The text was updated successfully, but these errors were encountered: