Releases: Cratis/Chronicle
Releases · Cratis/Chronicle
Release v10.7.0
Added
OnRetryEventSeverity
to Polly Resilience system. Defaults toDebug
Release v10.6.8
Fixed
- An exception that occurred when trying to update unique constraint index for events a constraint wasn't defined to handle. This is now fixed by not trying to update the index if the event type is not supported.
Release v10.6.7
Fixed
- Added missing binding for JsonSerializerOptions that the Chronicle client depends on
- Upgraded all frontend dependencies, hoping to fix a problem with the Workbench throwing an exception of
<Router/>
not configured - which it clearly is.
Release v10.6.6
No release notes
Release v10.6.5
Fixed
- Api project no longer needing a separate project to generate the swagger doc that we embed. Added a simple Mono.Cecil tool that embeds after the build is done.
- Switching the entire Api to use the gRPC services rather than having to have the full dependency to the Kernel.
- Fixing namespaces for all Api artifacts to be more consistent, cleaning up the generated proxies.
- Adding a shutdown timeout of Zero for the Kernel so that it stops immediately and does not wait for things.
Release v10.6.4
Fixed
- Fixing so that Reducers will not create an empty model instance if it fails.
- the
DefaultServiceProvider
used when no service provider is configured is now supporting scope creations. There will be no scoping, since it doesn't have any service collection and binding registration support. But will support the scenario of bare bone console apps.
Release v10.6.3
Fixed
- When using
.Join<>
and then using.On(m => m.Id)
- the Key/Id of the model, it never resolved the join. This fixes that and considers a join expression on the primary key to be a join expression to use forResolveJoin
operation which runs after events have been projected to catch any past events it should resolve properties from.
Release v10.6.2
Fixed
- Due to problems with ReadyToRun compiled version of the server when part of the Docker images, we decided to let the Workbench frontend be within the
wwwroot
folder and served as static files from the root Web server rather than use the Embedded option we provide.
Release v10.6.1
Fixed
- Putting back the Workbench in the Kernel. This was forgotten when creating the possibility for the embedded Workbench.
Release v10.6.0
Added
- Unique Constraints now support having more than one property per event for the
.On()
method. This will then become a composite key in the index that will be checked for uniqueness.