Class TransactionalCommandBehavior<TMessage, TResponse>

Namespace

Trellis.EntityFrameworkCore

Assembly

Trellis.EntityFrameworkCore.dll

Pipeline behavior that automatically commits staged changes after a successful command handler.

The behavior calls next to run the handler (which stages changes via repositories), then calls CommitAsync(CancellationToken) if the handler returned success. If the handler returned a failure Result<TValue>, no commit occurs and the staged changes are discarded when the DbContext is disposed.

This behavior is constrained to Mediator.ICommand<TResponse> messages — queries are not wrapped and incur no overhead.

Atomicity: EF Core wraps each SaveChanges call in an implicit database transaction, so all staged changes within a single handler are committed atomically. Cross-aggregate operations that share the same DbContext are automatically transactional.

public sealed class TransactionalCommandBehavior<TMessage, TResponse> : IPipelineBehavior<TMessage, TResponse> where TMessage : ICommand<TResponse> where TResponse : IResult, IFailureFactory<TResponse>

Type Parameters

TMessage

The command type.

TResponse

The result type, constrained to IResult and IFailureFactory<TSelf>.

Inheritance

object

TransactionalCommandBehavior<TMessage, TResponse>

Implements

IPipelineBehavior<TMessage, TResponse>

Inherited Members

object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.ReferenceEquals(object, object)

object.ToString()

Extension Methods

MaybeExtensions.AsMaybe<T>(T)

MaybeExtensions.ToResult<TValue>(TValue)

NullableExtensions.ToResult<T>(T?, Func<Error>)

NullableExtensions.ToResult<T>(T?, Error)

AggregateTestMutator.ClearMaybeField<TEntity, TValue>(TEntity, Expression<Func<TEntity, Maybe<TValue>>>)

AggregateTestMutator.SetMaybeField<TEntity, TValue>(TEntity, Expression<Func<TEntity, Maybe<TValue>>>, TValue?)

Constructors

TransactionalCommandBehavior(IUnitOfWork)

Pipeline behavior that automatically commits staged changes after a successful command handler.

The behavior calls next to run the handler (which stages changes via repositories), then calls CommitAsync(CancellationToken) if the handler returned success. If the handler returned a failure Result<TValue>, no commit occurs and the staged changes are discarded when the DbContext is disposed.

This behavior is constrained to Mediator.ICommand<TResponse> messages — queries are not wrapped and incur no overhead.

Atomicity: EF Core wraps each SaveChanges call in an implicit database transaction, so all staged changes within a single handler are committed atomically. Cross-aggregate operations that share the same DbContext are automatically transactional.

public TransactionalCommandBehavior(IUnitOfWork unitOfWork)

Parameters

unitOfWork IUnitOfWork

Methods

Handle(TMessage, MessageHandlerDelegate<TMessage, TResponse>, CancellationToken)

public ValueTask<TResponse> Handle(TMessage message, MessageHandlerDelegate<TMessage, TResponse> next, CancellationToken cancellationToken)

Parameters

message TMessage

next MessageHandlerDelegate<TMessage, TResponse>

cancellationToken CancellationToken

Returns

ValueTask<TResponse>