Update to SwiftFormat build based on 0.53.0 release #255
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
calda
commented
Jan 17, 2024
| @@ -35,7 +35,7 @@ | |||
| --someAny disabled # opaqueGenericParameters | |||
| --elseposition same-line #elseOnSameLine | |||
| --guardelse next-line #elseOnSameLine | |||
| --oneLineForEach wrap #preferForLoop | |||
| --onelineforeach convert #preferForLoop | |||
There was a problem hiding this comment.
Nick updated how the preferForLoop rule works, so this updates our configuration to preserve the behavior from previous versions nicklockwood/SwiftFormat#1490 (comment)
jqsilver
approved these changes
Jan 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Nick released SwiftFormat 0.53.0 recently. Previously we were using a build based on 0.52.x. This PR updates us to use a build based on 0.53.0.