Cointainer get new instance about dependency-injection HOT 8 CLOSED

In this case you two options:

1. Explicitly register App with the container using registerTransient. This tells the container that every time it is requested, a new instance should be returned.
2. Create a child container from the original using createChild This creates a new container that inherits the services of its parent. Manually register the App service with the child container as either singleton or transient and resolve App from the child.

Child containers are for more advanced scenarios such as wanting to have a parent container for your app, but a scoped child container for each web request. Child containers allow you to override services from the parent while still leveraging other instances managed by the parent. Usually if you just want to get new instances of a particular type, you just register it as a transient. So, options 1 is probably what you want. Another way you can accomplish transient registration automatically is to annotate the App class with the Transient annotation.

from dependency-injection.

I've added a few more tests. There is a test showing the API registerTransient to go along with the annotations tests.

from dependency-injection.

Ok, thanks, it works for me:

    class App {}

    var container = new Container();
    container.registerTransient(App, App);

    var app1 = container.get(App);
    var app2 = container.get(App);

    expect(app1).not.toBe(app2);

Can you tell me what do that args mean (App, App)? Why App on two places?

from dependency-injection.

The first arg is the key or type to register as. The second arg is the type of instance that key should resolve to. This enables scenarios like this:

container.registerTransient(AbstractType, ConcreteType);

So whenever someone requests AbstractType, they will get an instance of ConcreteType. This is used by the framework internally to allow it to work against abstractions of key services. I was thinking today that there should probably be a shortcut like this:

container.registerTransient(ConcreteType);

So you can easily use this when you don't have an abstraction. What do you think?

from dependency-injection.

I think that shortcut is prettier in my case.
If it could be worth to you to hear beginner's experience, from my perspective, I have expected to get new instance by default. Ok, in this moment I don't have an wide look to framework and what other aurelia tools need from it, but just saying.

from dependency-injection.

I'll go ahead and add the shortcut. That should be easy. Regarding default behavior, I've seen DI frameworks that do either. For purposes of Aurelia, the singleton approach works best. Since we don't really have docs yet...I think providing those and making the default behavior known should solve the problem.

from dependency-injection.

ok, I will watch the project get notif about shortcut

from dependency-injection.

It's in master now. I've also added a few more tests and re-arranged them a bit. So, hopefully that will help you see some more details. I still need to add more, but it's a start.

I'm currently adding the api docs to the source code. I'll commit that shortly. Then, I'm going to try to write up some preliminary documentation. You will be able to find that in the doc folder when it's pushed.

Hopefully, I will have another release of this module in the next day or two.

from dependency-injection.