To allow better intellisense support for signatures, the overloads allowing to specify services via a simplified form has been removed. From now on, services can be specified via the configuration object.
// Old format
Container.set(myToken, myValue);
// New format
Container.set({ id: myToken, value: myValue });To allow better intellisense support for signatures, the overloads allowing to specify services via a simplified form has been removed. From now on, services can be specified via the configuration object.
// Old format
@Service(myToken)
export class MyClass {}
// New format
@Service({ id: myToken })
export class MyClass {}The global, transient options had been removed in favor of scope option.
// Old format
@Service({ transient: true })
class MyTransientClass {}
@Service({ global: true })
class MySingletonClass {}
// New format
@Service({ scope: 'transient' })
class MyTransientClass {}
@Service({ scope: 'singleton' })
class MySingletonClass {}The Container.reset signature has changed. It's only possible to reset the current container instance you are calling
the function on, so the first containerId parameter has been removed.
// Old format
Container.reset(myContainerId, { strategy: 'resetValue' });
// New format
MyContainer.reset({ strategy: 'resetValue' });The option to add definitions as an array was removed. This was internally used, but exposed via the typing.
// Old format
Container.set([{ id: SomeClass, type: SomeClass }, { id: OtherClass, type: OtherClass }])
// New format
[{ id: SomeClass, type: SomeClass }, { id: OtherClass, type: OtherClass }].map(metadata => Container.set(metadata));- added support for specifying Container ID as
Symbol - re-enabled throwing error when
reflect-metadatais not imported
- internally the default container is also an instance of the ContainerInstance class from now on
Container.set()correctly enforces typing when used with aToken. Attempting to set something else than the Token type allows will raise a compile time error
The Container.remove method from now accepts one ID or an array of IDs.
// Old format
Container.remove(myServiceA, myServiceB);
// New format
Container.remove([myServiceA, myServiceB]);This was an undocumented way of calling the Service function directly instead of using it as a decorator. This option
has been removed and the official supported way of achieving the same is with Container.set. Example:
const myToken = new Token('myToken');
Container.set(myToken, 'test-value');
// Old format:
const oldWayService = Service([myToken], function myFactory(myToken) {
return myToken.toUpperCase();
});
const oldResult = Container.get(oldWayService);
// New format
const newWayService = Container.set({
// ID can be anything, we use string for simplicity
id: 'my-custom-service',
factory: function myFactory(container) {
return container.get(myToken).toUppserCase();
},
});
const newResult = Container.get('my-custom-service');
oldResult === newResult; // -> true, both equals to "TEST-VALUE"- added
eageroption toServiceOptions, when enabled the class will be instantiated as soon as it's registered in the container - added support for destroying removed services, when a service is removed and has a callable
destroyproperty it will be called by TypeDI
- [BREAKING] removed old, undocumented way of calling
@Servicedecorator directly - [BREAKING] renamed
MissingProvidedServiceTypeErrortoCannotInstantiateValueError - various internal refactors
- updated various dev dependencies
- generated sourcemaps contains the Typescript files preventing reference errors when using TypeDI with various build tools
- correctly export error classes from package root
Prior to this version when an unknown constructable type was requested from the default container it was added automatically
to the container and returned. This behavior has changed and now a ServiceNotFoundError error is thrown.
Until now resetting a container removed all dependency declarations from the container. From now on the default behavior
is to remove the created instances only but not the definitions. This means requesting a Service again from the container
won't result in a ServiceNotFoundError but will create a new instance of the requested function again.
The old behavior can be restored with passing the { strategy: 'resetServices'} to the ContainerInstance.reset function.
- [BREAKING] unknown values are not resolved anymore (ref #87)
- [BREAKING] resetting a container doesn't remove the service definitions only the created instances by default
- [BREAKING] container ID can be string only now
- default container ID changed from
undefinedtodefault - stricter type definitions and assertions across the project
- updated the wording of
ServiceNotFoundErrorto better explain which service is missing (#138) - updated various dev-dependencies
- various changes to project tooling
- fixed a bug where requesting service with circular dependencies from a scoped container would result in Maximum call stack size exceeded error (ref #112)
- fixed a bug where
@Inject-ed properties were not injected in inherited child classes (ref #102) - fixed a typing issue which prevented using abstract class as service identifier (ref #144)
- fixed a bug which broke transient services when
Container.reset()was called (ref #157) - fixed some typos in the getting started documentation
- added new type of dependency injection - function DI
- now null can be stored in the container for values
- fixed bug with inherited services
- fixed the way how global services work
- added javascript support
- removed deprecated
@Requiredecorator - added support for transient services
- now service constructors cannot accept non-service arguments
- added
@InjectManydecorator to support injection of "many" values - fixed the way how global services work
- added
Container.hasmethod
- added multiple containers support
- added grouped (tagged) containers support
- removed
providemethod, usesetmethod instead - deprecated
Requiredecorator. Use es6 imports instead or named services - inherited classes don't need to be decorated with
@Servicedecorator - other small api changes
- now
Handler'svalueaccepts a container which requests the value