Repository navigation
Releases
Releases · z4kn4fein/stashbox
Stashbox v5.21.0
Stashbox v5.20.0
Changed
- Consolidated the scoped/singleton service evaluation. When the evaluation fails with an exception, each subsequent resolution call will get the same exception.
- Track for cyclic resolution attempts of scoped/singleton services even through service locator style resolution calls.
- Refined exception messages.
- Replaced the
CircularDependencyExceptionwithResolutionFailedExceptionto lower the exception type redundancy.
Stashbox v5.19.3
Fixed
- #230: Unintentional exception throwing upon unresolvable named resolution.
Stashbox v5.19.2
Fixed
- #228: Optional value resolution with unknown type resolution
Stashbox v5.19.1
Fixed
- #228: Nullable optional parameter resolution
Stashbox v5.19.0
Added
- More configuration options for conforming to MS.DI extensions (
net10.0,net9.0, andnet8.0)enabledForCollectionRequestsswitch for.WithNamedDependencyResolutionForUnNamedRequests()configuration option..WithIgnoreServicesWithUniversalNameForUniversalNamedRequests()configuration option..WithForceThrowWhenNamedDependencyIsNotResolvable()configuration option..OverrideResolutionFailedExceptionWith<>()configuration option.
Stashbox v5.18.0
Fixed
- #213: Bug? Resolving Lazy or Func eagerly instantiates scoped/singleton wrapped services
Removed
PerScopedRequestLifetimelifetime.
Stashbox v5.17.1
Fixed
- #183:
ResolveAll()fails when service type hash collision. Thanks to @foriequal0 for the contribution.
Stashbox v5.17.0
Added
PreferEnumerableInCurrentoption toResolutionBehaviorenum. When this option is used upon enumerable resolution the following applies:- When both
CurrentandParentbehaviors are enabled, and the current container has the appropriate services, the resolution will prefer those and ignore the parent containers. When the current container doesn't have the requested services, the parent containers will serve the request.
- When both
Changed
- Enumerable resolution requests across child-parent containers resulted in the wrong order. Now, the resulting collection contains the parent services first and the child services at the end of the collection.
Stashbox v5.16.0
Added
- #165: A new
Overridetype that provides more control over dependency overrides. Usage:var service = container.Resolve<IService>([ Override.Of(instance, "name") ]);
WithExceptionOverEmptyCollection()container configuration option to control whether the container should return an empty collection or throw aResolutionFailedExceptionwhen a collection of services is requested but the wrapped service type is not resolvable.
Changed
- The
.Configure()and.RegisterResolver()methods now return with the actualIStashboxContainerto allow a fluent call chain.