This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to develop, this PR will be updated.
Releases
@freshgum/typedi@0.7.0
Minor Changes
658d830: The ContainerInstance.dispose method now runs semi-synchronously. This means that, immediately after calling it, the disposed property will be set to true. This is a semi-preemptive fix for situations where, due to the method previously being marked as async, the property would not be set in the same event loop iteration.
Patch Changes
8b13caa: The ContainerRegistry.removeContainer method no longer disposes already-disposed containers. This may have been an issue if a container was disposed, and then removeContainer was called; the call would always fail, as the registry attempted a disposal upon the container when doing so was invalid.
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to develop, this PR will be updated.
Releases
@freshgum/typedi@0.7.0
Minor Changes
disposed
property will be set totrue
. This is a semi-preemptive fix for situations where, due to the method previously being marked asasync
, the property would not be set in the same event loop iteration.Patch Changes
ContainerRegistry.removeContainer
method no longer disposes already-disposed containers. This may have been an issue if a container was disposed, and thenremoveContainer
was called; the call would always fail, as the registry attempted a disposal upon the container when doing so was invalid.