-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Fix false positives on rule first_where
#2638
Conversation
Generated by 🚫 Danger |
Source/SwiftLintFramework/Rules/Performance/FirstWhereRule.swift
Outdated
Show resolved
Hide resolved
Source/SwiftLintFramework/Rules/Performance/FirstWhereRule.swift
Outdated
Show resolved
Hide resolved
905ea08
to
d9113a7
Compare
@marcelofabri I think this can be merged, no? I fixed your comments quite a few days ago. |
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.
Sorry, I thought I had approved this one
No worries, thanks for approving! I'm not sure what the "perfect" procedure is here, can I just merge now given that you approved it and I myself don't see any reasons against merging? (Or to put it differently: Why didn't you merge right after approving it?) |
I didn't merge to make sure you had the final word on whether it's ready to merge as I know you have push access and can merge it. Sometimes a PR looks good to merge but the original author may prefer to not merge it (e.g. my own PR here #2633). Feel free to merge a PR whenever it's approved. |
Thanks for the explanation. Merging. 🎉 |
Fixes #1930.