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 5 and package manager support to be able to SPM AlamofireObjectMapper #1097

Merged
merged 3 commits into from
May 18, 2020

Conversation

kenji21
Copy link
Contributor

@kenji21 kenji21 commented May 13, 2020

Why

I want to add SPM support for AlamofireObjectMapper (tristanhimmelman/AlamofireObjectMapper#305)
So I need to be able to swift build and also swift test
Related issues: #1082 and #1089

What

Cherry-picked 4 commits from #1081, thanks to @emrcftci
Removed Sources symlink and fixed Package.swift to mark it Swift 5 (otherwise, it is swift 3... and the path to sources can't be customised)
Added test target in Package.swift to be able to swift test
Found 176 macOS tests while having 174 when runner with the xcworkspace (URLTransformTests were missing to macOS and tvOS test targets)

@kenji21
Copy link
Contributor Author

kenji21 commented May 13, 2020

travis doesn't run for PR ?

adding swift build and swift test in travis should be nice to keep SPM running OK

maybe adding linux support in SPM / travis should also be added (as another PR)

kenji21 referenced this pull request in openium/AlamofireObjectMapper May 14, 2020
@tristanhimmelman
Copy link
Owner

Hey, I've fixed the Travis integration so it should work now. Can you please merge master as I've merged a PR to upgrade to swift 5

@kenji21
Copy link
Contributor Author

kenji21 commented May 18, 2020

Just done it, waiting travis feedback

@kenji21
Copy link
Contributor Author

kenji21 commented May 18, 2020

Just updated SPM configuration line in README.md

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

Successfully merging this pull request may close these issues.

2 participants