-
Notifications
You must be signed in to change notification settings - Fork 110
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
Set legacy swift version #16
Conversation
I was about to make the same patch. If someone is still using XCode version 7, or a Swift version lower than 3, he can always use version 1.3.2 of this plugin. Can this pull request be merged and a new version of the plugin be made, please? |
I needed this immediately across quite a few machines, so I set up a fork here: https://github.com/bitjson/cordova-plugin-swift-support It's available via: cordova plugin add cordova-plugin-swift-support --save I also cleaned up the repo a bit, added "tests" that lint with @akofman – this is a fantastic project, thanks for getting it started! If you're still interested in actively maintaining it, I'd be happy to submit a pull request and direct my fork here. (Includes squashing @NiklasMerz's commits down into a single one here: bitjson@0994f93) |
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.
You might want to squash this all into a single commit, since several commits cancel each other out.
@bitjson I could doch that. But the merge will be one commit anyway. I had to try some stuff. Is there an easy option to conclude this in one commit? |
@NiklasMerz you can checkout the branch you made the changes on (looks like
Until
|
I have changed this to one commit like suggested @bitjson Thank you for this advice. Your suggested approach is faster than mine |
Guys it looks perfect ! Thanks for this work. |
I did this with my cordova plugin. I added my fork via the github url. After the next release I will change it to this npm package again Merged #16. — |
It is released and published on npm, you can use the version |
Hello guys, fyi I just added the availability to still use a legacy Swift codebase with the following preference : |
I had the issue that i could not build via CLI because the swift version was not set in build settings. close #15 .
I resolved this for by setting the project to swift version 3 for Xcode 8. Do you think this could be relevant for this plugin or is there a better approach to this?