Alamofire: Swift 3.0

Created on 14 Jun 2016  路  10Comments  路  Source: Alamofire/Alamofire

I hope this is the right place to post this. I would love to start testing Alamofire with swift 3.0 soon :) Thanks!

Most helpful comment

Please everyone be patient here. We'll certainly get a swift3 branch up as soon as possible. Unfortunately this year it's not going to be as easy as it has in the past. We need to make sure we update everything correctly to avoid causing everyone more harm than good.

If you find any helpful tips when trying to work through this yourself, please post them here! The more help the better.

All 10 comments

Luckily Xcode 8 might be able to use Alamofire as-is under Swift 2.3. We will be uploading a swift3 branch as soon as possible. I have to get the new stuff downloaded first. Plus, I'm not sure how big of a job it will be, considering they've changed how a lot of the Foundation stuff (NSURLSession APIs) are imported into Swift. Hopefully the auto migrator will work well.

After I upgraded to swift 3.0, just a mention :)
screen shot 2016-06-14 at 14 37 04

I would like to point out that I've got a Swift 3 compiling branch over here.

@avaidyam i have 150 error with your Swift 3 compiling branch :

Please everyone be patient here. We'll certainly get a swift3 branch up as soon as possible. Unfortunately this year it's not going to be as easy as it has in the past. We need to make sure we update everything correctly to avoid causing everyone more harm than good.

If you find any helpful tips when trying to work through this yourself, please post them here! The more help the better.

@mattcianna The tests don't compile; I just built the framework to continue migrating my own project over. I can't guarantee it even works. All I did was migration assistant and find/replace until it built. It's a good platform since there are no more build errors though.

@avaidyam I think it's very import that the tests do compile for Swift 3, as some frameworks are changing whether they are value or reference type. The tests will be needed to confirm this has no unexpected side results!

@dgsmith Totally understand! Problem: I was in the middle of phasing out Alamofire from my project (no hard feelings) and just needed the framework to compile so I could go ahead and do that.

Anyone is welcome to fork my fork and continue where I left off in the swift-3.0 branch. I figured since I had done some hard labor (Xcode is near useless for migration, honestly) I would share it.

Is there a release date for Alamofire for swift 3?

Please see #1316!

馃嵒

Was this page helpful?
0 / 5 - 0 ratings