IBOutlet reference not being properly converted

[jermowatson]

Steps to reproduce:
1.) Open up iSwift
2.) The following set of code.
@Property (strong, nonatomic) IBOutlet UITableView *AirportPlatesTableView;

Expected results:
@IBOutlet var AirportPlatesTableView: UITableView?

Actual results:
var airportICAOCode: IBOutlet?

Again unsure if this is something we the programmer needs to adjust after the conversion or of its something that is an error. Your call.

[drkameleon]

Yes, you're right. Good spot. (That's why feedback is great. I mean, I'm spotting things myself, write down most of them, then at some point forget about something and... it's gone...)

I'll look into it and I'll let you know. ;-)

[jermowatson]

No problem.

I worked out that most of them i.e. IBOutlet, UITable, UILabel etc seem to follow the same issue. :-)

On 28 Aug 2015, at 2:49 PM, Ioannis Zafeiropoulos notifications@github.com wrote:

Yes, you're right. Good spot. (That's why feedback is great. I mean, I'm spotting things myself, write down most of them, then at some point forget about something and... it's gone...)

I'll look into it and I'll let you know. ;-)

—
Reply to this email directly or view it on GitHub #23 (comment).

[drkameleon]

Well, basically it's whenever IBOutlet is used, nope?

---

I'm currently very close to getting it fixed.

[jermowatson]

Yeah I think so. From what I can see. I haven’t tried with others yet. Also I recommend your solution to someone I had a meeting with today :-P.

On 28 Aug 2015, at 3:30 PM, Ioannis Zafeiropoulos notifications@github.com wrote:

Well, basically it's whenever IBOutlet is used, nope?

I'm currently very close to getting it fixed.

—
Reply to this email directly or view it on GitHub #23 (comment).

[drkameleon]

Related Issue (just noticed it, and opened it myself - thought it's 5 mins away from being... closed :-) )

#26

[drkameleon]

Fixed as of the upcoming 1.4. ;-)

[jermowatson]

Excellent.

On 28 Aug 2015, at 4:04 PM, Ioannis Zafeiropoulos notifications@github.com wrote:

Fixed as of the upcoming 1.4. ;-)

—
Reply to this email directly or view it on GitHub #23 (comment).

[drkameleon]

Excellent.

:-)