Releases: microsoft/OpenAPI.NET
Releases · microsoft/OpenAPI.NET
v1.0.0-beta015
- Add smoke tests based on Apis.guru
- Allow relative URIs as per spec.
- Limit to allowed wildcard response statuses
- Fix parameter examples to be a map, not a list
- Fixed security requirement resolution
- Fixed resolution of parameter references
- Fixed issue with additionalProperties to allow it to be Boolean or schema
v1.0.0-beta014
- Bug fix: Serializing the
OpenApiAny
type fordouble
,float
, andlong
now works as expected. - Bug fix: Property is now serialized with
readonly
beingfalse
when it is in therequired
list for V2 to comply with the specification. - References are now loaded in a two-step process. First, the reference string is loaded in as is. Then, the reference resolver walks through the DOM to resolve the references. This allows circular references to be properly resolved.
v1.0.0-beta013
- Added
IOpenApiExtension
interface to be used when creating a new custom extension type. - Enabled the validation feature. By using
OpenApiValidator
, one can verify whether a givenOpenApiDocument
conforms to the specification based on the prescribed set of rules. More rules will be added in future releases.
v1.0.0-beta012
- Bug fix: Serializing and deserializing V2.0
formData
andbody
parameters - Bug fix: Deserializing V2.0
consumes
property
v1.0.0-beta011
- Throwing
OpenApiUnsupportedSpecVersionException
when spec version in document is not recognized by Reader
v1.0.0-beta010
- Bug fixes: Capitalization of parameter location in V2 serialization, top-level component reference serialization
- Reader will set specification version on
OpenApiDiagnostic
as a result of parsing
v1.0.0-beta009
- Support for OpenApi specificiation v3.0.1
- Recognize
formData
parameter when reading V2 documents
v1.0.0-beta008
v1.0.0-beta008