Releases: eventflow/EventFlow
Releases · eventflow/EventFlow
v0.62.3569
- New: Created
AggregateReadStoreManager<,,,>
which is a new read store manager
for read models that have a 1-to-1 relation with an aggregate. If read models get
out of sync, or events are applied in different order, events are either fecthed
or skipped. Added extensions to allow registration.UseInMemoryReadStoreFor<,,>
UseElasticsearchReadModelFor<,,>
UseMssqlReadModelFor<,,>
UseSQLiteReadModelFor<,,>
- New: Added
ReadModelId
andIsNew
properties to the context object that is
available to a read model inside theApply
methods in order to better support
scenarios where a single event affects multiple read model instances. - Minor: Applying events to a snapshot will now have the correct
Version
set
inside theApply
methods. - Minor: Trying to apply events in the wrong order will now throw an exception.
v0.61.3524
-
New: Support for
Microsoft.Extensions.DependencyInjection
(IServiceProvider
andIServiceCollection
) using theEventFlow.DependencyInjection
NuGet package.Add it to your ASP.NET Core 2.0 application:
public void ConfigureServices(IServiceCollection services) { services.AddMvc(); services.AddEventFlow(o => o.AddDefaults(MyDomainAssembly)); }
Or use it explicitly:
EventFlowOptions.New. .UseServiceCollection() ... .CreateServiceProvider();
-
New: Package
EventFlow.Autofac
now references Autofac 3.5.2 for .NET
framework 4.5.1 (down from Autofac v4.5.0) -
Fixed: Constructor injection of scoped instances into query handlers
v0.60.3490
- New: Implemented optimistic concurrency checks for MSSQL, SQLite and
Elasticsearch read models - New: Added .NET standard support for EventStore
- New: Delete read models by invoking
context.MarkForDeletion()
in an Apply method - Minor: Removed unnecessary transaction in EventStore persistance
- Fixed: Read model SQL schema is no longer ignored for
Table
attribute
v0.59.3396
- Fix: Commands are now correctly published when no events are emitted from a saga
after handling a domain event - Minor fix: Updated name of Primary Key for MSSQL Snapshot Store to be different
from MSSQL Event Store, so both can be used in the same database without conflicts
v0.58.3377
- Minor fix: Corrected log in
CommandBus
regarding events emitted due to command
v0.57.3359
- Fixed: AggregateException/InvalidOperationException when reading and updating
an aggregate from different threads at the same time usingInMemoryEventPersistence
- New: .NET standard 1.6 and 2.0 support for
EventFlow.MsSql
package
v0.56.3328
- New: Allow enums to be used in
SingleValueObject<T>
and protect from
undefined enum values
v0.55.3323
- Fixed: Re-populating events to read models that span multiple aggregates
now has events orderd by timestamp instead of sequence numbers, i.e., events
from aggregates with higher sequences numbers isn't forced last - New: Trigger sagas without the need of any domain events by using
ISagaStore.UpdateAsync(...)
- New: .NET standard 2.0 (still supports 1.6) support added to these
NuGet packages- EventFlow
- EventFlow.Autofac
- EventFlow.Elasticsearch
- EventFlow.Hangfire
- EventFlow.Sql
v0.54.3261
- Critical fix:
SagaAggregateStore
was incorrectly putting an object reference
into its memory cache causing an object already disposed exception when working with
sagas - New: Added LibLog, enable by
calling theIEventFlowOptions.UseLibLog(...)
extension
v0.53.3204
- New: Allow events to have multiple
EventVersion
attributes - Fixed:
ReflectionHelper.CompileMethodInvocation
now recognises
private
methods.