Bump EventFlow.Autofac from 0.72.3914 to 0.76.4014

[dependabot-preview]

Bumps EventFlow.Autofac from 0.72.3914 to 0.76.4014.

Release notes

Sourced from EventFlow.Autofac's releases.

v0.76.4014

• New: Mongo DB read model store Queryable:

  MongoDbReadModelStore readModelStore;
  IQueryable<TReadModel> queryable = readModelStore.AsQueryable();

• New: Moved publish of messages in RabbitMqPublisher to a new virtual
  method to ease reuse and customization
• Fixed: MongoDB read models no longer has the new() generic requirement,
  which aligns read model requirements with the rest of EventFlow

v0.75.3970

• Fix: When deserializing the JSON value "null" into a struct value like
  int, the SingleValueObjectConverter threw an exception instead of
  merely returning null representing an absent SingleValueObject<int> value

v0.74.3948

• Breaking: Renamed AspNetCoreEventFlowOptions.AddMetadataProviders()
  to AddDefaultMetadataProviders() and made AddUserClaimsMetadata opt-in
  in order to prevent policy issues.
• Fix: Allow explicit implementations of IEmit<> in aggregate roots
• Fix: Using .AddAspNetCore() with defaults now doesn't throw a DI
  exception.

v0.73.3933

• New: Configure JSON serialization:

  EventFlowOptions.New.
    .ConfigureJson(json => json
      .AddSingleValueObjects()
      .AddConverter<SomeConverter>()
    )

• New: ASP.NET Core enhancements:
  • New fluent configuration API for ASP.NET Core components:
    services.AddEventFlow(o => o.AddAspNetCore(c => {...})); (old syntax
    AddAspNetCoreMetadataProviders is now deprecated).
  • .RunBootstrapperOnHostStartup() runs bootstrappers together with ASP.NET
    host startup. Previously, this was done in AddAspNetCoreMetadataProviders
    and led to some confusion.
  • .UseMvcJsonOptions() adds EventFlow JSON configuration (see below) to ASP.NET Core,
    so you can accept and return Single Value Objects as plain strings for example.
  • .Add{Whatever}Metadata() configures specific metadata provider.
  • .AddUserClaimsMetadata(params string claimTypes) configures the new claims metadata
    provider (for auditing or "ChangedBy" in read models).
  • .UseLogging() configures an adapter for Microsoft.Extensions.Logging
  • .UseModelBinding() adds model binding support for Single Value Objects:

      [HttpGet("customers/{id}")]
      public async Task<IActionResult> SingleValue(CustomerId id)

... (truncated)

Changelog

Sourced from EventFlow.Autofac's changelog.

New in 0.76.4014 (released 2019-10-19)

• New: Mongo DB read model store Queryable:

  MongoDbReadModelStore readModelStore;
  IQueryable<TReadModel> queryable = readModelStore.AsQueryable();

• New: Moved publish of messages in RabbitMqPublisher to a new virtual
  method to ease reuse and customization
• Fixed: MongoDB read models no longer has the new() generic requirement,
  which aligns read model requirements with the rest of EventFlow

New in 0.75.3970 (released 2019-09-12)

• Fix: When deserializing the JSON value "null" into a struct value like
  int, the SingleValueObjectConverter threw an exception instead of
  merely returning null representing an absent SingleValueObject<int> value

New in 0.74.3948 (released 2019-07-01)

• Breaking: Renamed AspNetCoreEventFlowOptions.AddMetadataProviders()
  to AddDefaultMetadataProviders() and made AddUserClaimsMetadata opt-in
  in order to prevent policy issues.
• Fix: Allow explicit implementations of IEmit<> in aggregate roots
• Fix: Using .AddAspNetCore() with defaults now doesn't throw a DI
  exception.

New in 0.73.3933 (released 2019-06-11)

• New: Configure JSON serialization:

  EventFlowOptions.New.
    .ConfigureJson(json => json
      .AddSingleValueObjects()
      .AddConverter<SomeConverter>()
    )

• New: ASP.NET Core enhancements:
  • New fluent configuration API for ASP.NET Core components:
    services.AddEventFlow(o => o.AddAspNetCore(c => {...})); (old syntax
    AddAspNetCoreMetadataProviders is now deprecated).
  • .RunBootstrapperOnHostStartup() runs bootstrappers together with ASP.NET
    host startup. Previously, this was done in AddAspNetCoreMetadataProviders
    and led to some confusion.
  • .UseMvcJsonOptions() adds EventFlow JSON configuration (see below) to ASP.NET Core,
    so you can accept and return Single Value Objects as plain strings for example.
  • .Add{Whatever}Metadata() configures specific metadata provider.
  • .AddUserClaimsMetadata(params string claimTypes) configures the new claims metadata
    provider (for auditing or "ChangedBy" in read models).
  • .UseLogging() configures an adapter for Microsoft.Extensions.Logging

... (truncated)

Commits

• a141b08 Update release notes to align with latest PRs merged
• 57878d0 Merge pull request #699 from jepperc/develop
• 889897b Merge pull request #700 from ProH4Ck/feature/mongo-readmodel-empty-ctor
• 987c48a Merge pull request #701 from nishanth2143/patch-1
• 0aa07b1 Updated README.md file
• 922550d Merge branch 'develop' into feature/mongo-readmodel-empty-ctor
• 3583d98 Remove empty ctor requirement also on mongo readmodels
• 9396bcf move rabbitmq publish single message to own virtual method to allow log instr...
• f886e47 Merge pull request #696 from bryanscheele/feature/make-event-store-connection...
• 426d8b2 Make connectionNamePrefix nullable
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #52.