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

Update documentation for multiline_arguments_brackets and multiline_literal_brackets #4098

Merged
merged 1 commit into from
Aug 18, 2022

Conversation

chrisjf
Copy link
Contributor

@chrisjf chrisjf commented Aug 15, 2022

Hello SwiftLint Devs 👋

Here are the changes I've made to address the issue #4060 which include:

  • added two triggering examples that are a common style, to make it immediately obvious that they trigger the rules
  • also fixed a spelling mistake throughout the examples for the multiline_literal_brackets rule ("Gryffindor" is now correctly spelt)

If more information is needed, please see the description of the issue.

Thanks,
Chris

@SwiftLintBot
Copy link

SwiftLintBot commented Aug 15, 2022

12 Messages
📖 Linting Aerial with this PR took 0.35s vs 0.32s on master (9% slower)
📖 Linting Alamofire with this PR took 0.32s vs 0.33s on master (3% faster)
📖 Linting Firefox with this PR took 1.31s vs 1.32s on master (0% faster)
📖 Linting Kickstarter with this PR took 1.82s vs 1.83s on master (0% faster)
📖 Linting Moya with this PR took 0.23s vs 0.23s on master (0% slower)
📖 Linting Nimble with this PR took 0.22s vs 0.22s on master (0% slower)
📖 Linting Quick with this PR took 0.15s vs 0.15s on master (0% slower)
📖 Linting Realm with this PR took 1.16s vs 1.17s on master (0% faster)
📖 Linting SourceKitten with this PR took 0.2s vs 0.2s on master (0% slower)
📖 Linting Sourcery with this PR took 0.57s vs 0.57s on master (0% slower)
📖 Linting Swift with this PR took 0.94s vs 0.94s on master (0% slower)
📖 Linting WordPress with this PR took 2.07s vs 2.09s on master (0% faster)

Generated by 🚫 Danger

Copy link
Collaborator

@SimplyDanny SimplyDanny left a comment

Choose a reason for hiding this comment

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

Thanks! LGTM. Could you please rebase your branch to trigger another build?

…iteral_brackets

- added two triggering examples that are a common style, to make it immediately obvious that they trigger the rules
- also fixed a spelling mistake throughout the examples for the multiline_literal_brackets rule ("Gryffindor" is now correctly spelt)
@chrisjf chrisjf force-pushed the new-trigger-examples branch from bdcf065 to 37a4908 Compare August 18, 2022 06:13
@chrisjf
Copy link
Contributor Author

chrisjf commented Aug 18, 2022

Rebase done ✅

(Although last time I pushed, some of the buildkite phases of the CI failed. I didn't have time to investigate, but if it fails again, I'll take a look, and possibly ask for some pointers if needed.)

Thanks for the review. Good night 👋

@SimplyDanny
Copy link
Collaborator

Rebase done ✅

(Although last time I pushed, some of the buildkite phases of the CI failed. I didn't have time to investigate, but if it fails again, I'll take a look, and possibly ask for some pointers if needed.)

Thanks for the review. Good night 👋

Thank you for offering your help! The build was probably just unstable. I do not expect further issues.

@SimplyDanny SimplyDanny merged commit 1ef15f3 into realm:master Aug 18, 2022
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.

3 participants