# 0.12.0

- Update decorator typings for Typescript@5

# 0.11.5

- Fix injections in child class constructors leaking into base classes.

# 0.11.4

- Fix singleton and scoped values returning broken objects after their first resolution fails.

# 0.11.1

- Return `undefined` instead of `null` for single optional injections.

# 0.11.0

- Carry container instantiation parameters through factory context instantiation.
- Return `undefined` instead of `null` for single optional injections.

# 0.10.0

- Throw BindingResolutionError when unresolvable circular dependencies are encountered.
- Prevent multiple identical aliases on a binding from binding the alias multiple times.
- Allow injection of scope root on properties with @injectScope

# 0.9.3

- Fix duplicate entries in getAll due to parent bindings.

# 0.9.2

- Fix resolving multiple parent identifiers during injections.

# 0.9.1

- Fix resolving parent identifiers from injections.

# 0.9.0

- Introduce parameter injections for supplying data at request time.
  - Specify a param injection with the `@injectParam` decorator.
  - Pas parameters in an object map as second argument to `container.create()` and `container.get()`.
  - Get parameters from a factory function with `context.parameters`.
- Remove `@optional()` and `@all()` decorators. Use options argument in `@inject()` and `@injectParam()`.

# 0.8.0

- Improve error message when a class constructor binding is unresolved.
- Only resolve relevant bindings when resolving identifiers.
- Option to force resolve all bindings: `controller.resolveAllBindings`.
- Renamed `.toDynamicValue` to `.toFactory`.
- Support scope usage from toFactory bindings.
- `bind().provides()` now type-checks the target and must be used before binding.
- `@provides()` now type-checks the target class against the identifier.

# 0.7.1

- Fix typings when `bind().provides` is used before the binding target.

# 0.7.0

- Add `provides()` to binder to allow binding multiple identifiers to one resolution.

# 0.6.1

- Remove debugger statement.

# 0.6.0

## Features

- Add `@all()` decorator to specify all matching targets. Equivalent to`@inject(identifier, { all: true })`
- Add `Container.create` and factory `context.create` to directly instantiate and inject an arbitrary constructor.
- Add `bind(Constructor).toSelf()`.

## Refactors

- Clean up planner logic.
- Identifiers are tracked by the Binder, rather than the container.

# 0.5.0

## Features

- Introduce property injection.
- Add postInstantiate resolution step to component resolver.

## Refactors

- Insignificantly trim bundle size by directly requesting uuid/v4.

# 0.4.1

## Bug Fixes

- Fix getAll() returning a copy of the first registered value per matched binding.

## Refactors

- Removed build and test code from npm package.

# 0.4.0

## Bug Fixes

- Report the correct identifier in question when throwing over a circular dependency found in a constructor argument.
- Fix newly instantiated factories not receiving context after container.reset().
- Fix multiple @provides annotations on a scoped or singleton class producing multiple non-scoped instances of the class.
- Fix optional injection.
- Fix DependencyResolutionError message formatting.

## Refactors

- More Tests!
- Eliminate ComponentCreator concept by making DependencyGraphNode inherit properties of Binding and include resolution data.
- Determine instance equality by instanceId rather than creator object reference equality.
- Progress to pluggable dependency graphing and resolution.

# 0.3.1

- Fix auto-binding not attempting to use decorator data from the target of the binding, such as in `bind(identifier).to(autoBindableTarget)`
- Fix asScope bindings falling back to being singleton scopes when in an injected constructor argument.
- Fix identifier stack in error message on a cyclic dependency containing redundant or missing entries when asScope bindings are in play.

# 0.3.0

- Lower-case decorators to follow community standards and bring us back in line with InversifyJS.
- Fix asScope bindings acting as singleton scopes.

# 0.2.0

- Switch to using a dependency graph over imperative resolution.