Functional.CQS

Defines CQS-style contracts using Functional primitives:

• IQueryParameters<TResult>, a marker interface for query parameter objects that associates the query parameter object with the type of result that is returned when invoking the query handler
• IQueryHandler<TQuery, TResult>, for synchronous query handling
• IAsyncQueryHandler<TQuery, TResult>, for asynchronous query handling
• ICommandParameters<TError>, a marker interface for command parameter objects that associates the command parameter object with the type of error that can potentially occur when invoking the command handler
• ICommandHandler<TCommand, TError>, for synchronous command handling
• IAsyncCommandHandler<TCommand, TError>, for asynchronous command handling

What is CQS? Why use CQS?

Functional.CQS.AOP

Functional.CQS.AOP is a set of NuGet packages that provide decoration facilities over implementations of Functional.CQS contracts (listed above), specifically for aspect-oriented programming / applying cross-cutting concerns.

Why use Functional.CQS.AOP?

Library Usage Cookbook

You can find examples demonstrating how to use the various Functional.CQS.AOP libraries via the links below. Note that a general understanding of dependency injection, the decorator pattern, and onion architecture is assumed.

• Integrating Functional.CQS.AOP when using Pure DI (no dependency injection container)
• Integrating Functional.CQS.AOP when using the SimpleInjector dependency injection container

Information

Do you wish to contribute?

If you encounter problems with any Functional.CQS.AOP package, some documentation is unclear, or you have questions not adequately answered by the existing documentation, please report an issue.