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

Target Xcode 9.3 #247

Merged
merged 1 commit into from
Apr 10, 2018
Merged

Target Xcode 9.3 #247

merged 1 commit into from
Apr 10, 2018

Conversation

LinusU
Copy link
Contributor

@LinusU LinusU commented Apr 4, 2018

Opening this for early feedback

There are probably some more things to do, and I need to fix the tests (would love some pointers on fixing the tests 😄)

This ties into yonaskolb/XcodeGen#284

Short description 📝

Updates output to match what Xcode 9.3 would have produced.

Solution 📦

Changed the ordering of codeCoverageEnabled & shouldUseLaunchSchemeArgsEnv. Only wrote language if actually had a value.

Implementation 👩‍💻👨‍💻

  • Changed the ordering of codeCoverageEnabled & shouldUseLaunchSchemeArgsEnv.
  • Modified TestAction and LaunchAction to only print language if set.

GIF


This change is Reviewable

Sorry, something went wrong.

Unverified

No user is associated with the committer email.
@welcome
Copy link

welcome bot commented Apr 4, 2018

Thanks for opening this pull request! Please check out our contributing guidelines.

@tuistbot
Copy link

tuistbot commented Apr 4, 2018

1 Error
🚫 Please include a CHANGELOG entry.
You can find the guidelines at CHANGELOG_GUIDELINES.md.

Generated by 🚫 Danger

@pepicrft
Copy link
Contributor

pepicrft commented Apr 5, 2018

Good job @LinusU. You'd need to update the CHANGELOG to include your changes in the next version. Regarding the tests failing it seems that there's something wrong with the Danger script. It's a bit weird because it's not related to your changes.

My guess here is that danger-ruby-swiftlint version has been bumped and it's causing that bug that you see in the logs. Could you try pinning that dependency to the version 0.11.1?

# Gemfile
pod "danger-swiftlint", "0.11.1"

If that doesn't work we can disable swiftlint from Danger and open an issue to fix it on another PR. This PR should be blocked by this 😛

@LinusU
Copy link
Contributor Author

LinusU commented Apr 5, 2018

You'd need to update the CHANGELOG to include your changes in the next version.

Will do!

Regarding the tests failing [...]

The tests fail locally for me since part of the tests is cloning other repositories, opening, and then saving back the XcodeProj. Since these projects are still using Xcode 9.2, saving them will reorder the mentioned attributes, and remove the language property if it's empty. Therefore the tests "fail".

Potentially these projects would soon be updated, I could potentially go and submit a PR to each of them 😄

@pepicrft
Copy link
Contributor

pepicrft commented Apr 5, 2018

Can't we make this change in a way it's backward compatible with those projects that haven't been updated yet? @LinusU

@pepicrft
Copy link
Contributor

pepicrft commented Apr 9, 2018

@LinusU are you ok if I merge this one? I'll solve the issues on master and release a new version of the library.

@LinusU
Copy link
Contributor Author

LinusU commented Apr 10, 2018

Yes please! Sorry for the late response, currently on vacation 🏝🍹

@yonaskolb yonaskolb merged commit 0cdddc0 into tuist:master Apr 10, 2018
@welcome
Copy link

welcome bot commented Apr 10, 2018

Congrats on merging your first pull request! We here at xcode.swift are proud of you! Join our slack channel to talk to other contributors.

@yonaskolb
Copy link
Collaborator

Thanks @LinusU! Enjoy the vacation! 😄 🏝🍹

@pepicrft
Copy link
Contributor

Drink some Mojitos for us 🍹!

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.

None yet

4 participants