TemporalCommunity.Extensions.Analyzers 0.6.0

Temporal .NET Analyzers

Two opt-in analyzer packages provide compile-time guidance and IDE code fixes:

• Use TemporalCommunity.Extensions.Analyzers for replay-safety and handler-shape checks in any Temporal .NET workflow project.
• Add TemporalCommunity.DurableObjects.Analyzers for DurableObjects contract checks and generated clients. DurableObjects projects can use both packages.

Both packages include their IDE code fixes. There are no separate code-fix packages to install. Install the package appropriate for the project that declares workflows:

dotnet add package TemporalCommunity.Extensions.Analyzers

<PackageReference Include="TemporalCommunity.Extensions.Analyzers" Version="...">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageReference>

The general package does not depend on the DurableObjects runtime.

dotnet add package TemporalCommunity.DurableObjects.Analyzers

See the project sample for common diagnostics and fixes, or the .NET 10 file-based app for a no-project-file example. The file-based sample is pinned to 0.3.2; the catalog below describes this source tree.

General Temporal rules

These diagnostics apply to code lexically contained in a type with [Workflow]. They do not claim to inspect arbitrary external helper libraries; workflow replay tests remain necessary.

Update validators are synchronous and read-only. They validate the proposed arguments and reject an update by throwing; they must not issue workflow commands:

[WorkflowUpdate]
public Task<int> AddAsync(int value) => Task.FromResult(value);

[WorkflowUpdateValidator(nameof(AddAsync))]
public void ValidateAdd(int value)
{
    if (value < 0)
        throw new ArgumentOutOfRangeException(nameof(value));
}

DurableObjects rules

Generated DurableObject clients

TemporalCommunity.DurableObjects.Analyzers also generates one concrete client per supported contract. A contract such as ICounter produces CounterDurableObjectClient and a GetCounterClient factory extension. Synchronous contract queries remain available for source compatibility, while the concrete client adds asynchronous query methods and call-options overloads. Signals add Task-returning methods and call-options overloads, both using Signal-with-Start. Explicit wire names are preserved; default signal names strip trailing Async (queries do not). Dynamic signals are unsupported for all DurableObjects: DO0001 rejects dynamic signal declarations on contracts and object classes (including abstract ancestors), DO0005 rejects generated dynamic contracts, and worker registration/runtime enforce the same boundary. Named signals remain supported. A module initializer registers the concrete implementation so ordinary Get<ICounter> calls avoid DispatchProxy too.

Generation currently requires a public, top-level, non-generic contract. Existing applications that do not install the analyzer package continue to use the runtime proxy fallback.

Suppress a rule only after establishing that the reported code cannot execute in workflow context. Project-wide suppression of determinism rules is not recommended.