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

Small fixes to the iOS build #2965

Merged
merged 2 commits into from
Oct 1, 2024
Merged

Small fixes to the iOS build #2965

merged 2 commits into from
Oct 1, 2024

Conversation

badboy
Copy link
Member

@badboy badboy commented Oct 1, 2024

This will actually likely currently fail on CI, because the swiftlint we use there is older?
I have swiftlint 0.57 locally.

We might wanna update that check to Xcode 16 soon.

…ytes"

This reverts commit ad98555.

This lint was reverted, due to the "new" way actually swalling errors.
@badboy badboy requested a review from a team as a code owner October 1, 2024 10:57
@badboy badboy requested review from travis79 and removed request for a team October 1, 2024 10:57
@badboy
Copy link
Member Author

badboy commented Oct 1, 2024

Oh it actually doesn't fail, because CI uses swiftlint 0.53 which is so old, it doesn't have that (somewhat broken) new lint!

@badboy badboy enabled auto-merge (rebase) October 1, 2024 11:00
Copy link
Member

@travis79 travis79 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we reverting this when it was just changed to this 3 months ago?

ref: ad98555

@badboy
Copy link
Member Author

badboy commented Oct 1, 2024

Why are we reverting this when it was just changed to this 3 months ago?

ref: ad98555

Because I should have included the link: realm/SwiftLint#5263 (comment)

tl;dr: the way we changed it to is swallowing errors, and thus swiftlint actually reversed the decision and lints AGAINST this now.
That only happens with a newer swiftlint than we use on CI, but I have that newer one locally and thus make lint-swift fails for me. Given that we eventually upgrade CI and it doesn't fail right now we can land this.

Copy link
Member

@travis79 travis79 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, thanks for explaining! :)

@badboy badboy merged commit 4d54d96 into main Oct 1, 2024
29 of 30 checks passed
@badboy badboy deleted the small-fixes branch October 1, 2024 12:10
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