Subscribing On UITextfield (Control event, Editing changed)

I want to use RxSwift to get the text from a UITextField after the UIControlEvent Editing Changed is triggered.

In Order to do that:

I connected the textfield outlet from storyboard to my view controller like that.

@IBOutlet weak var currentPasswordTextField: UITextField!

and then on the didSet property of this textfield I tried this:

@IBOutlet weak var currentPasswordTextField: UITextField!{
    didSet{
        currentPasswordTextField
            .rx
            .controlEvent(.editingChanged)
            .asObservable()
            .subscribe(onNext: { (text) in
            //I want here to print the text after the editing changed. 
               print(text)
            })
            .disposed(by: disposeBag)
    }
}

but the text is Void not a string..

if anyone can help Id be grateful. thanks in advance.

P.S. I don't want to use IBActions.

Some points:

• asObservable() is unnecessary.
• you could subscribe to .rx.text.orEmpty directly, but then you will get events when the text field begins and ends editing.

Here you go:

@IBOutlet weak var currentPasswordTextField: UITextField!{
    didSet{
        currentPasswordTextField
            .rx
            .controlEvent(.editingChanged)
            .withLatestFrom(currentPasswordTextField.rx.text.orEmpty)
            .subscribe(onNext: { (text) in
                //I want here to print the text after the editing changed.
                print(text)
            })
            .disposed(by: disposeBag)
    }
}

---

Something else I thought of last night...

Putting this code in the didSet is going to be a problem. Rx code tends to be output centric, not input centric. Because of this, whatever goes in the subscribe will likely reference some other object that also has to exist and you are likely going to want to be able to reference other observables too.

What do I mean by input vs output centric?

Imperative code tends to be input centric, when you want to know what's going to happen when a button is tapped, you usually have one place to look, the button's action. However, if you want to understand everything that affects a particular label, activity indicator or any other output, you have to look all over the code. Every function in the view controller could be pushing information to the output and several of them likely are.

Declarative code tends to be output centric, when you want to know everything that affects a label's output, or what causes the activity indicator to show/hide, there is generally one place to look. However, if you want to understand everything that tapping a button does, you will have to look all over the code to figure it out. (A perfect example of this is a spreadsheet, if you want to know how the output for a particular cell is defined, you only need to look at the formula in that cell, but if you want to know all the cells that are affected by a particular cell, that's a pain.)

In my experience, the above is the hardest thing for programmers to wrap their heads around when working with Rx.