Coject.Core.Logging.AspNetCore 1.2.0

Coject.Core.Logging.AspNetCore

This package is a provider-neutral ASP.NET Core execution seam and transport base-class surface for custom procedures. It does not construct a database object, understand a legacy response type, or implement application authorization. The host supplies those parts through ICustomProcedureDalFactory<TDal, TRequest>, ICustomProcedureExecutor<TDal, TRequest, TLegacyResult>, and ICustomProcedureResponseMapper<TLegacyResult>.

The mapper returns CustomProcedureMappedResult.Single or .Batch, pairing the legacy response with the existing Core ICustomProcedureResult. The adapter then delegates semantic operational/audit mapping to ICustomProcedureTelemetry and hands authorization denials to the Contracts ICojectAuthorizationDeniedRecorder. Validation and denial paths expose only bounded safe codes to the default response mapper and never log request bodies, tokens, exception text, or provider values.

The current repository has no application-local CustomProcedureControllerBase and no generic legacy custom-procedure controller contract. Consequently this project intentionally does not reproduce controller-specific Baha behavior, attribute conventions, or DAL response classes. It does provide three explicit transport-shape base classes for Workshop-generated custom controllers. A provider/application adapter must implement provider-specific details at the three seams above.

Installation and dependency boundary

The current package version is 1.1.0. A minimal ASP.NET Core application can reference it with the framework and package references below:

<ItemGroup>
  <FrameworkReference Include="Microsoft.AspNetCore.App" />
  <PackageReference Include="Coject.Core.Logging.AspNetCore" Version="1.1.0" />
</ItemGroup>

This package declares the aligned runtime dependencies Coject.Core.Logging 1.3.0 and Coject.Core.Logging.Contracts 3.1.0.

When a Workshop-generated custom-controller artifact is compiled into the application, the artifact conditionally requires all three runtime packages:

<ItemGroup>
  <PackageReference Include="Coject.Core.Logging.Contracts" Version="3.1.0" />
  <PackageReference Include="Coject.Core.Logging" Version="1.3.0" />
  <PackageReference Include="Coject.Core.Logging.AspNetCore" Version="1.1.0" />
</ItemGroup>

These are generated-artifact dependencies: Contracts supplies the explicit event/action, transport-shape, and authentication contracts; Core supplies the custom-procedure descriptor and telemetry runtime; and AspNetCore supplies the controller base classes. They are not a request to make Coject.Workshop.Metadata depend on runtime packages. Workshop Metadata remains the separate ASP.NET-independent generation-time package.

Generated controller base classes

Workshop selects one base class from the explicitly declared CustomProcedureContractShape:

The three bases classify transport contract shape only. They do not classify business intent, select the event/action pair, select authentication, or represent Single versus Batch item cardinality. Those decisions remain explicit metadata/descriptor fields.

Explicit business event/action policy

The generated descriptor carries an explicitly declared Contracts event/action policy and Core procedure intent. Event and action are not inferred from procedure names, controller names, routes, HTTP verbs, CLR request/response types, or result counts. For example, a procedure named DeleteReport, a DELETE route, or a single-item result does not by itself select DataDeletion/Delete.

Declare the pair in Workshop metadata, such as DataRead/Read, DataCreation/Create, or DataModification/Execute; the metadata and descriptor validators then check compatibility with the declared intent and execution shape. Single/Batch is item cardinality, not a transport contract-shape decision.

Anonymous and authenticated procedures

CustomProcedureAuthenticationMode is explicit:

• Anonymous means no authorizer and no user ID are required. The adapter skips its authorizer hook for that descriptor. Workshop-generated metadata must omit userId, and no synthetic identity is created.
• AuthenticatedUser is the authenticated-caller mode. When the host provides ICustomProcedureAuthorizer<TRequest>, the adapter invokes it and maps its safe result to allowed, unauthorized, or forbidden execution. An explicit bounded userId may be carried as metadata, but it is never inferred from names, routes, HTTP context values, CLR types, or result counts.

Aligned package versions

Use the following versions when Workshop generation and ASP.NET Core runtime execution are consumed together:

The Workshop and Mapping packages are not dependencies of this ASP.NET Core package merely because their generated or mapped output is consumed by an application.