Cohesive.Adapters.OpenApi 0.1.0-alpha.121

Cohesive.Adapters.OpenApi

OpenAPI document emission and endpoint helpers for Cohesive API declarations.

Install

dotnet add package Cohesive.Adapters.OpenApi

Use When

• You want OpenAPI artifacts generated from Cohesive API declarations.
• You need endpoint helpers for publishing generated OpenAPI documents.
• You want OpenAPI, GraphQL, and TypeScript clients to share one semantic API source.

Example

using Cohesive.Adapters.OpenApi;
using Cohesive.Api;

var api = Api.Define("Shipping")
    .Entity<ShipmentDto>()
    .Query("Get")
        .Route("GET", "/shipments/{id}")
        .RouteParameter<string>("id")
        .Returns<ShipmentDto>()
        .Done()
    .Build();

var document = new OpenApiEmitter().Emit(api).Documents.Single();
app.MapCohesiveOpenApi(api);

Related Packages

• Cohesive.Api for API declarations.
• Cohesive.CodeGen.Cli for build-time artifact generation.

Public JSON contracts

Supply OpenApiEmitterOptions.JsonSerializerOptions to project a public document contract from the same serializer metadata used on the wire. This supports recursive records, explicit polymorphic cases and converter-backed scalar identifiers while keeping portable document storage admission separate. The CLI selects this profile with --shape-projection canonical-json for OpenAPI as well as shapes.

The profile rejects property-specific converters/number-handling overrides and polymorphic cases without explicit discriminators. Unknown converter output stays opaque; CLR implementation members are not substituted for a converter schema. Native document semantic validation remains authoritative. See typed portable JSON contracts for the projection boundary and qualification.

Nested serializer profiles

A property converter implementing IJsonValueSerializerProfile declares the frozen options it uses for the complete nested value. OpenAPI follows that profile instead of applying the envelope's naming and converter rules. WebJsonPropertyConverter<T> exposes its existing shared web profile. Each profile receives a separate type-to-schema cache within an emission; component names remain unique across profiles. Recursive references therefore preserve the selected profile even when the same CLR type is also serialized by the outer envelope. Mutable profiles and unrecognized custom property converters remain unsupported with explicit diagnostics. This support does not imply profile-aware TypeScript or GraphQL projection.