EventFlow.TestHelpers 0.50.3124

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package EventFlow.TestHelpers --version 0.50.3124
NuGet\Install-Package EventFlow.TestHelpers -Version 0.50.3124
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="EventFlow.TestHelpers" Version="0.50.3124" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add EventFlow.TestHelpers --version 0.50.3124
#r "nuget: EventFlow.TestHelpers, 0.50.3124"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install EventFlow.TestHelpers as a Cake Addin
#addin nuget:?package=EventFlow.TestHelpers&version=0.50.3124

// Install EventFlow.TestHelpers as a Cake Tool
#tool nuget:?package=EventFlow.TestHelpers&version=0.50.3124

A collection of test helpers used to help develop event and read model stores for EventFlow. Please
     note that this is an alpha initial release of the test helpers package and content is subject
     to change.

Product Compatible and additional computed target framework versions.
.NET Framework net451 is compatible.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.0.5003-alpha 99 6/21/2023
1.0.5002-alpha 1,691 11/11/2022
1.0.5001-alpha 141 3/15/2022
1.0.4748-alpha 202 9/9/2021
1.0.4617-alpha 219 6/11/2021
0.83.4713 11,736 9/7/2021
0.82.4684 307 8/30/2021
0.82.4659 339 6/17/2021
0.81.4483 441 12/14/2020
0.80.4377 584 10/1/2020
0.79.4216 473 5/13/2020
0.78.4205 481 5/11/2020
0.77.4077 933 12/10/2019
0.76.4014 721 10/19/2019
0.75.3970 518 9/12/2019
0.74.3948 574 7/1/2019
0.73.3933 578 6/11/2019
0.72.3914 582 5/28/2019
0.71.3834 608 4/17/2019
0.70.3824 704 4/11/2019
0.69.3772 657 2/12/2019
0.68.3728 738 12/3/2018
0.67.3697 855 10/14/2018
0.66.3673 737 9/28/2018
0.65.3664 750 9/22/2018
0.64.3598 782 8/27/2018
0.63.3581 866 8/7/2018
0.62.3569 1,143 7/5/2018
0.61.3524 816 6/26/2018
0.60.3490 912 6/18/2018
0.59.3396 906 5/23/2018
0.58.3377 931 5/13/2018
0.57.3359 890 4/30/2018
0.56.3328 984 4/24/2018
0.55.3323 908 4/24/2018
0.54.3261 879 2/25/2018
0.53.3204 914 1/25/2018
0.52.3178 882 11/2/2017
0.51.3155 899 10/25/2017
0.50.3124 887 10/21/2017
0.49.3031 1,100 9/7/2017
0.48.2937 1,183 7/11/2017

New: While EventFlow tries to limit the about of painful API changes, the
introduction of execution/command results are considered a necessary step
towards as better API.
Commands and command handlers have been updated to support execution
results. Execution results is meant to be an alternative to throwing domain
exceptions to do application flow. In short, before you were required to
throw an exception if you wanted to abort execution and "return" a failure
message.
The introduction of execution results changes this, as it allows
returning a failed result that is passed all the way back to the command
publisher. Execution results are generic and can thus contain e.g. any
validation results that a UI might need. The `ICommandBus.PublishAsync`
signature has changed to reflect this.
from
```csharp
Task<ISourceId> PublishAsync<TAggregate, TIdentity, TSourceIdentity>(
ICommand<TAggregate, TIdentity, TSourceIdentity> command)
where TAggregate : IAggregateRoot<TIdentity>
where TIdentity : IIdentity
where TSourceIdentity : ISourceId
```
to
```csharp
Task<TExecutionResult> PublishAsync<TAggregate, TIdentity, TExecutionResult>(
ICommand<TAggregate, TIdentity, TExecutionResult> command,
CancellationToken cancellationToken)
where TAggregate : IAggregateRoot<TIdentity>
where TIdentity : IIdentity
where TExecutionResult : IExecutionResult
```
Command handler signature has changed from
```csharp
Task ExecuteAsync(
TAggregate aggregate,
TCommand command,
CancellationToken cancellationToken);
```
to
```csharp
Task<TExecutionResult> ExecuteCommandAsync(
TAggregate aggregate,
TCommand command,
CancellationToken cancellationToken)
```
Migrating to the new structure should be seamless if your current code base
inherits its command handlers from the provided `CommandHandler<,,>` base
class.
Breaking: Source IDs on commands have been reworked to "make room" for
execution results on commands. The generic parameter from `ICommand<,,>`
and `ICommandHandler<,,,>` has been removed in favor of the new execution
results. `ICommand.SourceId` is now of type `ISourceId` instead of using
the generic type and the `ICommandBus.PublishAsync` no longer returns
`Task<ISourceId>`
To get code that behaves similar to the previous version, simply take the
`ISourceId` from the command, i.e., instead of this
```csharp
var sourceId = await commandBus.PublishAsync(command);
```
write this
```csharp
await commandBus.PublishAsync(command);
var sourceId = command.SourceId;
```
(`CancellationToken` and `.ConfigureAwait(false)` omitted fromt he above)
Breaking: Upgraded NuGet dependency on `RabbitMQ.Client` from `>= 4.1.3`
to `>= 5.0.1`