Closed raphaelcruzeiro closed 8 years ago
Rockin' - I think this will also need the travis file updating to Xcode 8 - it's currently 7.3
@orta: I haven't bothered yet with the travis file as Quick and Nimble are still not Swift 3 ready. As soon as they have it working we can start migrating the tests and configuring travis to use the xcode8 image.
👌 cool
Also, I just realised that the ~
operator is not working as expected as of Beta 6. I really wish I could run those tests now...
Quick and Nimble have been successfully migrated to Swift 3 (Xcode 8 Beta 6). I'm gonna start fixing the tests for this branch later today 🤘🏼
🤘🏼
👍
I've just merged #203 to master, so you might have a little bit more porting to do - sorry!
No worries. I'll rebase this branch and port the new code.
I have converted the tests to Swift 3 and all is well except for the Priority operator which has a problem of precedence. I have tried fixing it as per SE-0077 but it seems that I got it wrong as the following test fails to build:
it("should operate on a single constraint") {
var constraint: NSLayoutConstraint!
constrain(view) { view in
constraint = (view.width == 200 ~ 100)
}
expect(constraint.priority).to(equal(100))
}
I will take a deeper look into that later today and hopefully a commit will follow 😉
@orta @robb I had no luck in getting the ~
operator working with the new precedencegroup
😞
XCode 8 GM didn't break anything on this branch 😮
Should also consider switching these deps to CocoaPods, every time I look at the build fails it's because of Carthage using the GitHub API
Anyway, @raphaelcruzeiro - is the ~
and rpecedencegroup a blocker?
@orta I pushed a commit switching to CocoaPods. Hopefully travis will at least get to trying to build the tests. About the ~
, I really have no idea how to solve that. From what I understood of SE-0077, the precedence group is correctly set for this operator. However, when trying to build the tests I get a CartographyTests/PrioritySpec.swift:22:49: Ambiguous reference to member '~'
.
Hrm, I haven't looked at Swift 3 but I remember this tweet perhaps you can try making the name CartographyPriorityGroup
?
I can rename the precedence group to avoid possible name clashes but this will most likely not solve the operator problem.
I've made a note and some PR changes in https://github.com/raphaelcruzeiro/Cartography/pull/1
Submitted another PR to hopefully fix CI - https://github.com/raphaelcruzeiro/Cartography/pull/2
awww, we got one green
@orta 🎉
env NSUnbufferedIO=YES
the random things you have to do to appease the Xcode gods
OK, IMO this is good to go, will give it a look over tomorrow and give this a good to go, IMO this library has been used in production long enough that this should be the 1.0 given there there is now literally thousands of people relying on it in production
The project builds and seems to run correctly. Still need to update Quick and Nimble and fix the tests.