Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump Autofac from 4.9.2 to 6.4.0 in /src/Miningcore #25

Closed

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jun 1, 2022

Bumps Autofac from 4.9.2 to 6.4.0.

Release notes

Sourced from Autofac's releases.

v6.4.0

  • Fix typos in exception messages (#1301, #1302, #1323)
  • Enable open generic assembly scanning to use WithMetadata and generate metadata (#1299 - thanks @​romerod!)
  • Package targets .NET 6 TFM (#1306)
  • README included in NuGet package (#1295, #1308)
  • Symbols published in .snupkg format (#995, #1309)
  • Fix issue where changing type parameter names caused generic resolution to fail (#1315, #1316)
  • Added generic delegates to make registering lambda components easier (#1320, #1321)
  • Optimization of reflection activation for components that only have one constructor (#1325)

The new feature to be aware of here is the generic delegates for making lambda registrations easier (#1320, #1321). It makes resolving dependencies in lambdas more straightforward.

The old way meant injecting an IComponentContext and resolving the dependencies manually.

builder.Register(
  ctx =>
  {
    var dep1 = ctx.Resolve<IDependency1>();
    var dep2 = ctx.Resolve<IDependency2>();
    return new Component(dep1, dep2, "configuration-value");
  });

That old way still works and is not deprecated. You can keep doing that.

However, you can now skip the manual resolutions and just provide the dependencies as the parameters to the lambda:

builder.Register(
  (IDependency dep1, IDependency dep2) =>
    new Component(dep1, dep2, "configuration-value"));

If you need both the context and dependencies for advanced cases, you can do that, too.

builder.Register(
  (IComponentContext ctx, IDependency dep1) =>
  {
    var dep2 = ctx.Resolve<IDependency2>(new NamedParameter("p", "someValue"));
    new Component(dep1, dep2, "configuration-value");
  });

v6.3.0

  • Modules can now be registered conditionally using an OnlyIf clause. (#1235, #1272)
  • Delegate factories will no longer allow parameters with the name value to inject by name as that's a reserved word in property setter methods. (#1275)
  • IAsyncDisposable instances that have not been activated are correctly disposed when the scope is disposed. (#1285)
  • There are now generic overloads for TryResolveNamed and TryResolveKeyed. (#1263, #1287 - thanks @​v0idzz!)

... (truncated)

Commits
  • 25cc97b Semver => 6.4.0 for release.
  • ed6b1d9 Merge pull request #1325 from autofac/feature/single-constructor-optimisation
  • efa63ac Remove old comment.
  • e54ac1e Update following PR feedback; added IConstructorSelectorWithEarlyBinding.
  • a09c78d Make sure we check if the activator is disposed in the new paths; also change...
  • 32b3a22 Add MatchingSignatureConstructorSelector tests.
  • 6ce4318 Resolve warning
  • c8bedac Performance optimisations for single-constructor reflection paths.
  • 56af5b3 Merge pull request #1323 from autofac/fix/warning-typo
  • c69da54 Change sync disposal warning message from efficient -> inefficient
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [Autofac](https://github.com/autofac/Autofac) from 4.9.2 to 6.4.0.
- [Release notes](https://github.com/autofac/Autofac/releases)
- [Commits](autofac/Autofac@v4.9.2...v6.4.0)

---
updated-dependencies:
- dependency-name: Autofac
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jun 1, 2022
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Dec 1, 2022

Superseded by #40.

@dependabot dependabot bot closed this Dec 1, 2022
@dependabot dependabot bot deleted the dependabot/nuget/src/Miningcore/dev/Autofac-6.4.0 branch December 1, 2022 06:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants