New scope: TyphoonScopeNonContained

[jasperblues]

The final scope to implement will be TyphoonScopeNonContained

• This will do dependency injection on objects outside the container, by advising/wrapping init methods
• Optionally will allow specifying which init method(s) get wrapped

This scope provides a way to avoid the _'anemic model anti-pattern'_. Consider the following case:

• An object is emitted eg CoreData
• In OO such an object should have properties as well as methods, however in order to provide useful methods, we sometimes need collaborators.
• Traditionally we're left with a choice to either forgo DI and hard-wire dependency or settle for anemic model objects.

This scope aims to address this problem. It should be used sparingly as there are some drawbacks, the main being:

• Assumes all instances of a given class are configured with the same dependencies.

[alexgarbarev]

Maybe move 'lazy' property to TyphoonScopeLazySingleton and remove property? I don't like 'NonContained' name because it is not clear (maybe better InitSwizzled or something else)

[jasperblues]

@alexgarvarev I agree. this means a somewhat intimidating menu if scopes to learn. But it eliminates the other concept/duplication entirely. And there's been some confusion there.

[jasperblues]

After debating this with @alexgarbarev we've decided to drop it for now. The drawbacks and added complexity seem to outweigh the merits.

• Users wishing to have 'rich' model objects can fairly easily instruct Typhoon to inject a given instance with little extra boilerplate. (Some frameworks provide hooks for this). On the other-hand there's some serious drawbacks to the 'global' configuration that some DI containers impose when they use this approach. . . it shouldn't be encouraged in Typhoon.