Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swift 2.0 not supported #5

Closed
dickverbunt opened this issue Jul 13, 2015 · 6 comments
Closed

Swift 2.0 not supported #5

dickverbunt opened this issue Jul 13, 2015 · 6 comments

Comments

@dickverbunt
Copy link

It doesn't support the new syntax of Swift 2.0 yet. Will this be added in the near future?

I know it uses Alamofire and it's not fully Swift 2.0 yet but has a working swift-2.0 branch.

@varenc
Copy link
Contributor

varenc commented Jul 29, 2015

hey @dickverbunt,

we hear you on this! We're likely going to be dropping Alamofire support in the next update which will make it easier for us to make a swift-2.0 branch as well.

@dickverbunt
Copy link
Author

@varenc Thanks for the update. Looking forward to it.

@drscotthawley
Copy link

Please do point out this lack of support for Swift 2 in the docs & Tutorial on the Dropbox website(s). Wasted a lot of time trying to fix syntax errors & resolve dependencies, after going through the install/tutorial before I found this thread.

@rpearl
Copy link
Contributor

rpearl commented Sep 3, 2015

Hi all,

I have opened up swift 2 support, for now in a separate branch until swift 2 and Xcode 7 are out of beta. The swift-2.0 branch is here.

This requires the latest Xcode 7 beta 6, available on Apple's developer site.

We currently still depend on Alamofire (2.0.0 branch from the swift-2.0 tree)--I wonder if anyone has any opinions as to whether we should work for a standalone library or whether continuing to depend on Alamofire is okay.

I'll leave this open until we merge to master.

@tkrajacic
Copy link

Libraries that don't have dependencies are always easier to manage. Alamofire is not that big a deal, since it is well tested and maintained, but if you can get rid of it it would definitely be better.

@rpearl
Copy link
Contributor

rpearl commented Oct 1, 2015

Swift 2 is now merged to master!

@rpearl rpearl closed this as completed Oct 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants