Darrel

See spec https://www.rfc-editor.org/rfc/rfc7578.html

OpenAPI specification example of multipart forms. https://spec.openapis.org/oas/v3.1.0#encoding-object-example In OpenAPI 3.0, JSON Schema isn't rich enough to describe multipart forms, so you may need a combination of schema object and encoding...

I do worry about creating extensions that look like they are native to the SDK. It could cause a supportability issue.

This is blocked on OpenAPI 3.1 support as the patternedProperties keyword is not supported in OpenAPI 3.0

For union and exclusion types that are non-scalar, a discriminator is required to enable runtime differentiation between the returned type. ```yaml MyResponseType: oneOf: - $ref: '#/components/schemas/Cat' - $ref: '#/components/schemas/Dog' -...

If possible we should prevent the RequestFactory from being emitted, but probably still emit the model or we could cause cascading errors.

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

A work in progress https://github.com/tavis-software/tavis.openapi but it will be finished soon.

``` ``` This metadata should give ``` https://graph.microsoft.com/v1.0/reports/getOffice365ActiveUserDetail(period='{period}') (we have this) https://graph.microsoft.com/v1.0/reports/getOffice365ActiveUserDetail(period='{period}')/content ``` However, the metadata doesn't match the behavior of the APIs in most cases. In reality, the first...

@baywet That's probably the easiest path forward