Emended OpenAPI v3.1 definition used by typia and nestia.
OpenApi is a namespace containing functions and interfaces for emended
OpenAPI v3.1 specification. The keyword "emended" means that OpenApi is
not a direct OpenAPI v3.1 specification (OpenApiV3_1), but a little
bit shrunk to remove ambiguous and duplicated expressions of OpenAPI v3.1
for the convenience of typia and nestia.
For example, when representing nullable type, OpenAPI v3.1 supports three ways.
In that case, OpenApi remains only the third way, so that makes typia and
nestia (especially @nestia/editor) to be simple and easy to implement.
{ type: ["string", "null"] }
{ type: "string", nullable: true }
{ oneOf: [{ type: "string" }, { type: "null" }] }
Here is the entire list of differences between OpenAPI v3.1 and emended OpenApi.
Emended OpenAPI v3.1 definition used by
typia
andnestia
.OpenApi
is a namespace containing functions and interfaces for emended OpenAPI v3.1 specification. The keyword "emended" means thatOpenApi
is not a direct OpenAPI v3.1 specification (OpenApiV3_1), but a little bit shrunk to remove ambiguous and duplicated expressions of OpenAPI v3.1 for the convenience oftypia
andnestia
.For example, when representing nullable type, OpenAPI v3.1 supports three ways. In that case,
OpenApi
remains only the third way, so that makestypia
andnestia
(especially@nestia/editor
) to be simple and easy to implement.{ type: ["string", "null"] }
{ type: "string", nullable: true }
{ oneOf: [{ type: "string" }, { type: "null" }] }
Here is the entire list of differences between OpenAPI v3.1 and emended
OpenApi
.Author
Jeongho Nam - https://github.com/samchon