3.0.0-beta.3

• Enabled non nullable types
• New Provider features
• Allow to use symbols or numbers as names and tags
• isBoundNamed, isBoundTagged

3.0.0-beta.2

New features

• Container.prototype.createChild #408
• Add AMD bundle to the NPM package #419

Bug Fixes

• Container.getAll does not return named bindings #405

3.0.0-beta.1

Breaking changes

• Kernel is now Container
• getServiceIdentifierAsString is not a method of Container anymore.
• PlanAndResolveArgs is now NextArgs in middleware.
• Contextual constraints

New features

• Container Merge
• Container Options
• Named defaults
• container.getAllNamed
• container.getAllTagged

Non-functional improvements

• Performance has been improved
• Major internal refactor

Notes

All changes can be explored here.

This is a beta release, we are going to do multiple beta releases before releasing 3.0.

My goal is to include:

• Non-nullable types
• Async/await providers (awaiting TypeScript 2.1)

I'm also considering a second refactor in which all the functions in planning and resolution process will become pure. For example, at the moment some functions either return or throw an error. Instead of that, it could be better to always return Either<Error, interfaces.Target[]>. By doing this, the planner and resolver will become pure (at the moment they are stateless but not pure).

The Container (old Kernel) is the only stateful entity and will be the place in which we throw exceptions. We can also explore not throwing and returning Either<Error, T> when resolving. This is something that I need to think about and might never happen...

2.0.1

Fixes #385

2.0.0

Migrated to TypeScript 2.0 RC. Refer to https://github.com/inversify/inversify-basic-example to see how to configure your dev environment.

2.0.0-rc.14

Breaking changes

We have migrated to TS 2.0 and type definitions are now auto-generated but they are incompatible with inversify-dts. Plaase refer to #362 to have updates on how far we are from resolving these issues.

Changes

• Run test with PhantomJS Karma launcher
• Allow singleton dynamic value injection
• Solves #330
• Migrated from typings to @types
• Updated docs
• Removed need for reference to reflect-metadata.d.ts
• Allow abstract classes to be used as identifiers #363

2.0.0-rc.13

• New feature : Circular dependencies detailed error (#353)
• Breaking change: Allow toDynamicValue to access the current context (#351)

2.0.0-rc.12

• Property injection support

2.0.0-rc.11

@remojansen Adding some help based on feedback from ##338 adc5343
@greenkeeperio-bot chore(package): update karma-chrome-launcher to version 2.0.0 (#343) … cb9e238
@Offirmo Update activation_handler.md (#344) … 8ea5f64
@Offirmo Update get_all_named_tagged.md (#346) … 467afb5
@remojansen Fixed #345 (#347) 741ea4e
@remojansen Implements #348 (#349) … 0d87faf
@remojansen Update README.md 9aca721
@remojansen Update package.json cde2aba

2.0.0-rc.10

• Breaking change property injection is now available via https://github.com/inversify/inversify-inject-decorators
• Fixed #338