ResultCommander 2.1.2
See the version list below for details.
dotnet add package ResultCommander --version 2.1.2
NuGet\Install-Package ResultCommander -Version 2.1.2
<PackageReference Include="ResultCommander" Version="2.1.2" />
<PackageVersion Include="ResultCommander" Version="2.1.2" />
<PackageReference Include="ResultCommander" />
paket add ResultCommander --version 2.1.2
#r "nuget: ResultCommander, 2.1.2"
#:package ResultCommander@2.1.2
#addin nuget:?package=ResultCommander&version=2.1.2
#tool nuget:?package=ResultCommander&version=2.1.2
ResultCommander
Library featuring a command handler pattern for both synchronous and asynchronous operations.
Uses a functional Result approach for failure-prone operations.
To utilize all features using Autofac is required.
Features
- Synchronous and asynchronous command handler definitions
- Definitions and base implementations of commands
- Supports decorators and adapters via Autofac's methods
Description
There are two command types - one that only returns a Result and one that returns an additional entity contained within the Result.
Every handler must return a Result struct which determines whether the operation succedeed or not, handlers may or may not return additional results contained within the Result struct - this is defined by the handled comand.
Installation
To register handlers with the DI container use the ContainerBuilder or IServiceCollection extension methods provided by the library:
builder.AddResultCommander(assembliesToScan);
To register decorators or adapters use the methods available on ResultCommanderConfiguration like so:
builder.AddResultCommander(assembliesToScan, options =>
{
options.AddDecorator<FancyDecorator, ISyncCommandHandler<SimpleCommand>();
});
You can register multiple decorators and they'll be applied in the order that you register them - read more at Autofac's docs regarding decorators and adapters.
Documentation
Documentation available at https://docs.result-commander.mikym.me/.
Example usage
<b> You should never throw exceptions from within handlers, they should be exception free - instead return appropriate error results (and catch possible exceptions).</b> Library offers a simple error catching, logging and exception to result error decorators for uses where writing try-catch blocks becomes a pain - but remember that these results will never be as informative as manually returned proper result error types.
A command without a concrete result:
public SimpleCommand : ICommand
{
public bool IsSuccess { get; }
public SimpleCommand(bool isSuccess = true)
=> IsSuccess = isSuccess;
}
And a synchronous handler that handles it:
public SimpleSyncCommandHandler : ISyncCommandHandler<SimpleCommand>
{
Result Handle(SimpleCommand command)
{
if (command.IsSuccess)
return Result.FromSuccess();
return new InvalidOperationError();
}
}
A command with a concrete result:
public SimpleCommandWithConcreteResult : ICommand<int>
{
public bool IsSuccess { get; }
public SimpleCommand(bool isSuccess = true)
=> IsSuccess = isSuccess;
}
And a synchronous handler that handles it:
public SimpleSyncCommandHandlerWithConcreteResult : ISyncCommandHandler<SimpleCommand, int>
{
Result<int> Handle(SimpleCommand command)
{
if (command.IsSuccess)
return 1;
return new InvalidOperationError();
}
}
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 is compatible. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net6.0
- AttributeBasedRegistration (>= 2.1.1)
- Microsoft.Extensions.Options (>= 7.0.1)
- Remora.Results (>= 7.2.3)
- Remora.Results.Analyzers (>= 1.0.0)
-
net7.0
- AttributeBasedRegistration (>= 2.1.1)
- Microsoft.Extensions.Options (>= 7.0.1)
- Remora.Results (>= 7.2.3)
- Remora.Results.Analyzers (>= 1.0.0)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on ResultCommander:
| Package | Downloads |
|---|---|
|
ResultCommander.Autofac
Library featuring a command handler pattern. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 2.2.4 | 284 | 7/23/2024 |
| 2.2.3 | 352 | 1/22/2024 |
| 2.2.2 | 327 | 11/22/2023 |
| 2.2.1 | 221 | 11/20/2023 |
| 2.2.0 | 213 | 11/20/2023 |
| 2.1.6 | 299 | 8/18/2023 |
| 2.1.5 | 295 | 8/8/2023 |
| 2.1.4 | 294 | 7/10/2023 |
| 2.1.3 | 299 | 6/25/2023 |
| 2.1.2 | 512 | 5/10/2023 |
| 2.1.1 | 340 | 4/4/2023 |
| 2.1.0 | 389 | 3/14/2023 |
| 2.0.9 | 401 | 2/21/2023 |
| 2.0.8 | 454 | 1/9/2023 |
| 2.0.7 | 414 | 1/9/2023 |
| 2.0.6 | 516 | 11/21/2022 |
| 2.0.5 | 461 | 11/21/2022 |
| 2.0.4 | 474 | 11/21/2022 |
| 2.0.3 | 496 | 11/19/2022 |
| 2.0.2 | 469 | 11/19/2022 |