pipeline-decorator

You compose cross-cutting concerns by wrapping command handlers with ordered decorators, enforcing one concern per decorator. This separates logging, validation, and transactions from business logic by leveraging dependency injection to assemble the pipeline.

You enforce decorator execution order explicitly during pipeline composition. The Skill supports explicit decorator ordering, allowing deterministic behavior by defining the sequence in which decorators like ValidationDecorator and LoggingDecorator wrap the handler.

Yes, the decorator pattern for command handlers primarily applies to .NET applications using CQRS patterns. It leverages dependency injection to wire base and concrete decorators around handlers in a Clean Architecture setup.

The best way to separate cross-cutting concerns is applying the decorator pattern to compose modular, reusable pipelines around application handlers. This maintains a clear separation between decorators and handlers without polluting business logic.

Dependency injection assembles decorators by wrapping base and concrete implementations around handlers. You configure the DI container to register ordered decorators like ValidationDecorator and LoggingDecorator, then invoke HandleAsync on the command.

No, the pipeline composition supports one decorator per concern. To maintain deterministic behavior and clear separation, you enforce a single decorator for each cross-cutting concern like logging or validation within the explicit execution order.