Method Injection?

[ronak2121]

Hi,

I'm wondering if Typhoon offers a method to do method injection?

Here's what Spring Framework offers in Java:

http://docs.spring.io/spring/docs/4.0.2.BUILD-SNAPSHOT/spring-framework-reference/htmlsingle/#beans-factory-method-injection

If not, I imagine the fallback is to grab a reference to the default TyphoonFactory and get a new object...(there by coupling our code to Typhoon?)

Thanks,

Ronak

[jasperblues]

@ronak2121

We don't currently have this feature.

Alternatives:

Not coupled directly to Typhoon:

• Use TyphoonFactoryProvider : http://www.typhoonframework.org/docs/latest/api/interface_typhoon_factory_provider.html

Still dependency injection, but coupled to Typhoon

• Use TyphoonComponentFactoryAware (can be replaced with a mock during testing).

*Ticket number #131 (coming in a few days) will allow injection of assembly interfaces by type. Still coupled to Typhoon, because these interfaces are a sub-class of TyphoonAssembly, but more domain-specific in that they relate to your app rather than the the TyphoonComponentFactory. (can be replaced with a mock during testing).

Typhoon's default scope:

Note that in Spring the default scope is singleton. This makes sense on a web-server when any given use-case could be invoked at a time. On mobile and desktop we typically serve one use-case at a time, so the default-scope is TyphoonScopeObjectGraph

This scope means that when you resolve a component, any instance that is shared during resolution, will be treated as a singleton.

Eg:

- (id)checkoutFormViewController
{
    ///injected with checkoutView and checkoutViewValidator
}

- (id)checkoutView
{
    //Injected with checkoutViewValidator
}

- (id)checkoutViewValidator
{
    //with ObjectGraph scope, this is treated as a shared instance between 
    //checkoutFormViewController and cehckoutView, but they're not retained by Typhoon, 
    //so when the use-case is done the whole lot goes away. 
}

Because of this difference in default scope, it was recently common to make a view controller TyphoonComponentFactoryAware (as in the sample app), in order to resolve an object graph and move on to the next use-case. However the recommended approach is now:

• TyphoonFactoryProvider
• (or Feature Non-invasive version of TyphoonComponentFactoryAware #131 is you don't mind being somewhat coupled to Typhoon).

[jasperblues]

@ronak2121 Thoughts?

[jasperblues]

NB: I don't recommend using TyphoonAssistedFactoryProvider for the above kind of thing until issue #145 is fixed.

TyphoonAssistedFactoryProvider is available now, but will be officially endorsed when we release Typhoon v2.0 (in a few weeks).

[jasperblues]

@ronak2121 closing. . . if you have any further feedback, please raise a new issue (proposed API) or reopen (discuss further).