Justin Black

Yes, if we could add a link or specify that 262 section 21.2.1 applies in the pattern section in the validation portion of the spec, that would meet my needs.

This warning also makes sense when an enum contains a value not allowed by types

Can we get some guidance on this? Should we send `%00` when serializing null as [this post](https://stackoverflow.com/questions/31254490/how-to-send-null-in-http-query-string) suggests? From my reading of RFC 6570 that empty list, empty dict and...

Some Possible Paths forward here, which would require breaking changes to openapi: 1. disallow clients from sending (rfc defined) undefined values. Undefined values are: [], {}, null any dict where...

For reference here, this should work better if the client is regenerated using openapi v6.2.0 [Docs for that generator include inline types or links to reference types](https://github.com/OpenAPITools/openapi-generator/blob/master/samples/openapi3/client/petstore/python/docs/apis/tags/FakeApi.md#array_of_enums) [Endpoints include type...

Did you find any other solutions?

Why are you sending json lines data as binary when plain text will work? It says that it is utf8 encoded so it could be string. Where is the spec...

The approach to supporting different content types can be seen in the response body deserializer. They are explicitly handled on a case by case basis for types like - plain...

My mistake, plain text is not on the list in python.

So my preference is not to support undefined content types unless there is significant prior work showing how the content type is sent and significant user need (lots of people...