Releases: dolittle/vanir
Releases · dolittle/vanir
Release v9.24.0
Added
- Support for using the ASP.NET Core
[Authorize]
attribute and its policies for authorization
Release v9.23.0
Added
- [C#]
IExecutionContextManager
interface - making it possible not lock one into the implementation. This enables more predictability for automated tests, which could potentially have side-effects with its async local implementation for holding current.
Release v9.22.2
Added
- [C#] Ability to run validators on instance by consuming
IValidators
interface inDolittle.Vanir.Backend.Validation
namespace and call eitherValidate()
orValidateAsync()
Release v9.22.1
Added
- Noddin
Release v9.22.0
Added
- [C#] Added a default public filter that will forward all events applied/committed as public - this behavior can be overridden by setting
PublishAllPublicEvents
in theBackendArguments
used inAddVanir()
method to false. You can then use the Dolittle configuration callback to configure your filter instead: https://dolittle.io/docs/tutorials/event-horizon/ - [C#] All types adorned with the [Projection] attribute are automatically registered as projections. Read more here: https://dolittle.io/docs/tutorials/projections/
Changed
- [C#] Upgraded to version 8.4.0 of the SDK
Release v9.21.1
Fixed
- [C#] During GraphQL calls, all validators for a type using FluentValidation is now included automatically. Not just the first it discovers.
Release v9.21.0
Added
- [C#] Added a callback to the BackendArguments to be able to configure the Mongo DB settings before they're frozen for the client instance
Release v9.20.2
Fixed
- Apollo + GraphQL dependencies moved from React to Web - which is more correct. If you don't use React, you'll then get the dependencies we really rely on.
Release v9.20.1
Changed
- @dolittle/projections upgraded to v2.1.0 for supporting Guid conversion to and from Mongo
Release v9.20.0
Added
- Support for @graphroot decorator to be able to root resolver classes and resolver methods to build a structured schema.
- Preliminary support for calling event mutations directly - without type details - you give it a JSON string as event content / payload