application/x-www-form-urlencoded request content type is not handled properly

[baywet]

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

[baywet]

when implemented, we should clear the appsettings.json to be able to ship self-contained executable

[darrelmiller]

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

[baywet]

meeting notes:

• objects with scalar properties properties supported
• objects with complex properties not supported
• collections are not supported

stand-up new packages for:

• Go
• typescript
• java
• dotnet

Create the issues for the other languages