Eternet.Mediator.EndpointModel 1.0.22

Eternet.Mediator.EndpointModel

Stable endpoint transport descriptors, manifest contracts, readers, and build support used to move endpoint semantics from mediator contracts into downstream consumers without re-interpreting the contracts locally.

Public surface

This package is the narrow shared contract between the generator stack and downstream projection consumers.

It exposes:

• EndpointManifest as the root transport artifact
• EndpointDescriptor and related request/response/route DTOs
• EndpointOperationSemantic for additive public API intent (Query, Create, Update, Delete, Upsert)
• AuthorizationEndpointAttribute and AuthenticationOnlyEndpointAttribute as neutral endpoint authorization metadata
• GatewayProjectionDescriptor for gateway-specific route metadata
• EndpointManifestJson for serialization
• EndpointRouteNormalizer for stable route normalization
• ContractAssemblyEndpointManifestReader to read the generated manifest carrier from a compiled contracts assembly
• EndpointManifestArtifact helpers for the sidecar file name and path

Build integration

When a contracts project sets:

<EternetGenerateEndpointManifest>true</EternetGenerateEndpointManifest>

the buildTransitive targets in this package:

1. read the manifest embedded in the compiled *.Contracts.dll when available,
2. fall back to reflection-based manifest reconstruction only for compatibility,
3. emit <AssemblyName>.eternet.endpoint-model.json,
4. copy that sidecar next to the built assembly,
5. and include it in the produced .nupkg so downstream consumers restore it automatically.

Role in manifest-driven projection

The supported manifest-driven projection model is:

1. Eternet.Mediator.EndpointManifest.Generator extracts endpoint semantics once from Roslyn symbols.
2. The dedicated manifest generator emits an embedded manifest carrier into the contracts assembly.
3. Eternet.Mediator.EndpointModel materializes that carrier as a sidecar artifact during build and pack.
4. A downstream projector consumes the sidecar first, then the embedded carrier, and only falls back to reflection for older assemblies.

That keeps request binding, HTTP verb, route template, and gateway projection metadata authoritative in the contracts repo instead of rediscovering them downstream.

API semantic metadata

EndpointDescriptor.OperationSemantic carries the additive API semantic inferred from the public request contract.

Inference precedence is:

1. explicit HTTP and route attributes
2. public IEndpointQuery/Create/Update/Delete/Upsert interfaces
3. legacy-compatible IApiQuery/Create/Update/Delete/Upsert interfaces
4. legacy base-type inference
5. legacy operation-name fallback

This means a contracts repo can opt into richer semantics without rewriting explicit transport attributes that already ship in production.

For compatibility, OperationSemantic = Upsert still projects to CrudOperation = Update in the manifest. Downstream consumers that understand the richer field can read OperationSemantic; older consumers can continue using CrudOperation.

More detail

See for the end-to-end flow and repo responsibility split.

See for the current contract-first authoring defaults, MVC shim catalog, and review checklist.