appsquickly/Typhoon

Poweful dependency injection for iOS & OSX (Objective-C & Swift)

Jasper Blues

@jasperblues

Typhoon is a DI container so you should obtain your built instance from Typhoon. . . via the assembly interface.

Take a look at the Quick Start for example.

https://github.com/appsquickly/Typhoon/wiki/Quick-Start

Roman Temchenko

@iThinker

Oh. Do you mean that having [Class new] objects fully configured is a side effect?

Yeah. I've seen it.

And I've looked at some 3rd paty videos.

I am just not familiar with DI

Jasper Blues

@jasperblues

No. Typhoon won’t touch you class unless you ask for it from Typhoon.

Roman Temchenko

@iThinker

YOu know, we don't have it usually in iOS .:D

Jasper Blues

@jasperblues

DI is a common design pattern. And it applies in all OO languages. . . (though some, eg Ruby, tend not to use/need a library to manage it).

Once you understand DI you’ll have another tool for solving problems.

You don’t necessarily need a library to do DI <—— If you can understand how it works https://github.com/appsquickly/Typhoon-example

Roman Temchenko

@iThinker

Well, I've done only iOS. And I've heard previously about DI. But i've not seen it on any project.

I understand what you mean.

Jasper Blues

@jasperblues

https://github.com/appsquickly/Typhoon-example <—— Here’s an example for you

Roman Temchenko

@iThinker

Why not everything is created in assemblies? For example UINavigationController.

Jasper Blues

@jasperblues

Why are some classes defined in Typhoon and some not?

Roman Temchenko

@iThinker

I am sorry. I did not get your sarcasm.

Jasper Blues

@jasperblues

no, i want you to clarify you question.

Roman Temchenko

@iThinker

Then I did not get your question. There is a RootController. It can show other controllers. But instead of asking assembly for UINavigationController, it takes UIViewController and wraps it into UINavigationController. I thought in case of DI, UINavigationController should be created by factory with proper root view controller.

Jasper Blues

@jasperblues

My question was asking you to clarify your question.

Is that clear?

I understand your question now.

The idea is to define the key actors in your assembly. Arguably that could be a UIViewController defined in the assembly. You can try that modification if you like.

Roman Temchenko

@iThinker

Ok. I see. Thank you. One last quick question. How to create object using its factory method. (In Cocoa it is called Class Cluster, in other languages it is Abstract Factory I believe)

Jasper Blues

@jasperblues

Yes, that’s right.

Roman Temchenko

@iThinker

That was a question. How to do it?

Jasper Blues

@jasperblues

Yes, that’s right . . . class cluster is related to abstract factory. If you want to do this with Typhoon you can:

Use Typhoon Option Matcher https://github.com/appsquickly/Typhoon/wiki/Typhoon-Option-Matcher

Create a custom factory backed by Typhoon. (Inject the whole assembly into you custom factory, and then use it to emit the correct object).

https://github.com/appsquickly/Typhoon/wiki/What%20can%20be%20Injected#injecting-the-assembly-itself

clear?

Roman Temchenko

@iThinker

Looks like it is not what I wanted. I have [Class instanceForCustomer], [Class instanceForContractor]. And I wanted factory to return those instances. But with additional injection.

So I should either move all configuration to Assembly. Or don't use Assembly at all for it.

I've found.

Jasper Blues

@jasperblues

I see. . If you want it factory method to be on the class, you can have the class method use Typhoon. This would have to be a separate factory.

Roman Temchenko

@iThinker

It is Factory Definitions section I think.

Jasper Blues

@jasperblues

Your class method would look something like:

- (instancetype) myTyphoonAssembledInstance {
    MyAssembly *assembly = [[MyAssembly new] activate];
   //Decide what instance to return
  //Ask Typhoon to return it. 
}

This is not a common thing to do with Typhoon. It may or may not be a good idea for your specific case.

Roman Temchenko

@iThinker

I wanted not to mess with Typhoon inside my own classes. I just wanted to encapsulate some bahvipour and use factory methods.

Jasper Blues

@jasperblues

I can’t think of another way to do what you’re asking.

(with Typhoon)

I don’t think it will help you here.

Roman Temchenko

@iThinker

- (SwordFactory *)swordFactory
{
    return [TyphoonDefinition withClass:[SwordFactory class]];
}

- (Sword *)blueSword
{
    return [TyphoonDefinition withFactory:[self swordFactory] 
        selector:@selector(swordWithSpecification:) 
        parameters:^(TyphoonMethod *factoryMethod) {

            [factoryMethod injectParameterWith:@"blue"];
        }];
}

I thought I will be able to use this. But I did not dig into it yet.

Jasper Blues

@jasperblues

That feature is for creating a definition (object that can participate in dependency injection by Typhoon) that get emitted from another object (such as a legacy class).

Roman Temchenko

@iThinker

This is like my situation. I take a legacy class. Get object from it. Inject additional info and return it.

Jasper Blues

@jasperblues

Is it? Ok then.

I misunderstood that from the initial description.

Jasper Blues

@jasperblues

let us know how it works for you :)

Where communities thrive

People

Repo info

Activity