-
Notifications
You must be signed in to change notification settings - Fork 86
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
[WIP] Swift 3.0 #94
[WIP] Swift 3.0 #94
Conversation
let substring = string.substringWithRange(range) | ||
|
||
escaped += substring.stringByAddingPercentEncodingWithAllowedCharacters(allowedCharacterSet) ?? substring | ||
var allowedCharacterSet = CharacterSet.urlQueryAllowed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated this from Alamofire code. It seems that they are dropping iOS 8.x on the new release. Maybe we should do the same? (If not, this needs to be reverted and converted to Swift 3.0)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my point of view it is ok to drop iOS 8 support. If someone needs it, we are open for a Pull Request :)
Also, I chose to not mark the classes as |
I think Circle hasn't update to the GM yet |
github "jspahrsummers/xcconfigs" "0.9" | ||
github "ReactiveCocoa/ReactiveCocoa" "v4.2.2" | ||
github "ReactiveCocoa/ReactiveCocoa" "v4.0.0-alpha.3" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for some reason, this was changed when I updated Nimble
¯_(ツ)_/¯
So, the macOS and iOS builds are passing, but the Reactive Cocoa isn't. From what I've seen, 4.x won't support Swift 3, so we'd need to wait for 5.0. I have no idea if Thoughts? |
hello @marcelofabri |
So, is there any plan to migrate Heimdallr to Swift 3.0? |
Should we use https://github.com/ReactiveCocoa/ReactiveSwift instead of RAC 4? If so, there's already a 1.0.0-alpha.1 release we can use. |
I've updated the dependencies now that Nimble and Quick have stable versions and also updated the code to use ReactiveSwift instead of ReactiveCocoa. However, I had to comment all the |
Excuse me, I don't have much details into the project but as a user of Heimdallr, I would like to understand why is there - historically - blocking dependencies still here? Or is it that we can DL this branch, exclude RAC, and get things working? |
@BabyAzerty If you use CocoaPods, you can use my fork without the RAC subspec (it's optional), so you can migrate your project to Swift 3.0 while waiting this PR to be merged. Just change your Podfile: pod 'Heimdallr', git: 'https://github.com/marcelofabri/Heimdallr.swift.git', branch: 'swift-3.0' While I can't speak for the maintainers, I think it'd be useful to make the RAC extension another repository to make it easier to manage, but I don't know how complex that would make things. |
@marcelofabri Thank you so much for this and sorry for our late response here. We've been a bit busy the last couple of weeks but I would like to rekindle the discussion here again.
I think if we want to have full compatibility with Objc and Swift we'll require both
I like that idea! I believe it would make the project way easier to maintain. Since we are also internally moving away from heavy RAC usage in our project, it might be the right direction for |
We decided that we are fine with splitting up the repository and removing RAC as a dependency for this repository. @marcelofabri Do you want to tackle that? I think you already provide a working Swift 3 fork without the RAC subspec? We'll create a second repository for the reactive extensions when we have a stable RAC release. Let me know if I can help you out in any way 😊 |
@bckr I'm currently traveling, so it's unlikely that I'm able to work on this for the next ~2 weeks. The fork currently have a RAC subspec, but it's just not working 100%. I've allowed edits from maintainers, so feel free to start from my fork if you wanna handle this. |
@marcelofabri Will do! Thanks! |
# Conflicts: # Heimdallr/Core/Heimdallr.swift # Heimdallr/Core/OAuthAccessTokenDefaultParser.swift # Heimdallr/Core/OAuthAccessTokenParser.swift # HeimdallrTests/Core/HeimdallrSpec.swift
Hi all, |
Is there anything I can do to help the Swift 3 migration? |
This adds support to Swift 3.0. It's still WIP:
Update tests to run on iOS 10: they seem to be failing on the Simulator with the same issue mentioned here: https://forums.developer.apple.com/thread/51071 and http://stackoverflow.com/questions/38456471/secitemadd-always-returns-error-34018-in-xcode-8-beta-4-in-ios-10-simulatorI think this should be done on a later PR, since it'll probably need to create an app target so the unit tests could be run on a host app (with an Entitlements file)