-
Notifications
You must be signed in to change notification settings - Fork 226
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
Update Commandant #623
Comments
We're using the last Commandant version to include an Xcode project, meaning that if we update we can no longer include Commandant as a git submodule without some decent build system changes. That's also why the unit tests you linked to failed when you upgraded. |
Ah I didn't notice that! Thanks for the explanation :) |
The latest Commandant 0.17.0 still have its Xcode project, so what does it mean? |
🤔 You're absolutely right, I was remembering a PR that was planning on removing it, but clearly that didn't happen. My mistake 😬. |
Fixed in #625. |
Now that SourceKitten requires Swift 5.0 to build, we can update
Carthage/Commandant
to the latest version, which drops theResult
dependency.I started doing that, but it broken some unit tests and it wasn't obvious to me what the fix should be.
The text was updated successfully, but these errors were encountered: