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

SwiftLint recommends a double run when fixing #784

Merged
merged 11 commits into from
Feb 27, 2023

Conversation

cclauss
Copy link
Contributor

@cclauss cclauss commented Feb 22, 2023

https://github.com/realm/SwiftLint#xcode recommends

If you wish to fix violations as well, your script could run swiftlint --fix && swiftlint instead of just swiftlint. This will mean that all correctable violations are fixed while ensuring warnings show up in your project for remaining violations.

https://github.com/realm/SwiftLint#auto-correct

Standard linting is disabled while correcting because of the high likelihood of violations (or their offsets) being incorrect after modifying a file while applying corrections.

Summary of Changes

Fixes # (if applicable - add the number of issue this PR addresses)

Test Data or Screenshots

By submitting this pull request, you are confirming the following:
  • I have reviewed the Contribution Guidelines.
  • I have performed a self-review of my own code.
  • I have updated my repository to match the develop branch.
  • I have included test data or screenshots that prove my fix is effective or that my feature works.
  • I have checked that all tests work and swiftlint is not throwing any errors/warnings.

cclauss and others added 3 commits February 22, 2023 08:13
https://github.com/realm/SwiftLint#xcode recommends
> If you wish to fix violations as well, your script could run `swiftlint --fix && swiftlint` instead of just `swiftlint`. This will mean that all correctable violations are fixed while ensuring warnings show up in your project for remaining violations.

https://github.com/realm/SwiftLint#auto-correct
> Standard linting is disabled while correcting because of the high likelihood of violations (or their offsets) being incorrect after modifying a file while applying corrections.
JeneaVranceanu
JeneaVranceanu previously approved these changes Feb 22, 2023
@JeneaVranceanu
Copy link
Collaborator

@cclauss Ping me when you are done with this PR.

@cclauss cclauss marked this pull request as draft February 22, 2023 10:04
@cclauss cclauss marked this pull request as ready for review February 22, 2023 12:44
@cclauss
Copy link
Contributor Author

cclauss commented Feb 22, 2023

Please re-review.

janndriessen
janndriessen previously approved these changes Feb 22, 2023
Copy link
Collaborator

@janndriessen janndriessen left a comment

Choose a reason for hiding this comment

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

If tests pass - LGTM!

.swiftlint.yml Outdated
force_try: error
# force warnings (disabled above)
# force_cast: error
# force_try: error
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we need these commented out lines?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed.

.swiftlint.yml Outdated Show resolved Hide resolved
@cclauss
Copy link
Contributor Author

cclauss commented Feb 27, 2023

@JeneaVranceanu wrote:

@cclauss Ping me when you are done with this PR.

Ready for review.

@JeneaVranceanu JeneaVranceanu merged commit 69b52b2 into web3swift-team:develop Feb 27, 2023
@cclauss cclauss deleted the patch-1 branch February 27, 2023 21:32
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.

4 participants