style: apply swiftformat across the codebase#30
Merged
Conversation
Contributor
|
Important Review skippedToo many files! This PR contains 151 files, which is 1 over the limit of 150. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (151)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
ElonPark
force-pushed
the
chore/apply-swiftformat
branch
from
July 15, 2026 14:56
702a376 to
be82c62
Compare
ElonPark
changed the title
Run swiftformat with the new project configuration. Notable mechanical changes include import sorting, attribute placement, multiline string indentation, trailing commas in multi-element lists, and Swift Testing test names converted to raw identifiers by swiftTestingTestCaseNames. Two manual accompaniments keep the build green: - CodingUserInfoKey.resilientDecodingErrorReporter is written as `: CodingUserInfoKey = .init(...)!` because the propertyTypes rule miscompiles the multiline `= CodingUserInfoKey(...)!` form into a tuple. - The @DefaultCodable test doubles are wrapped in `swiftformat:disable propertyTypes` regions, since an explicit type annotation breaks the wrapper's generic parameter inference. swift test passes in both debug (303) and release (295) configurations. Claude-Session: https://claude.ai/code/session_017kn3Hf2khxiFy1TqimTGx9
ElonPark
force-pushed
the
chore/apply-swiftformat
branch
from
July 15, 2026 15:02
be82c62 to
23dbcef
Compare
Base automatically changed from
fix/polymorphic-lossy-array-null-outcome
to
main
July 15, 2026 15:13
4 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Run
swiftformat .across the codebase (153 files) with the house-style configuration (2-space indent, 120-column limit). Notable mechanical changes:testable-bottom), attribute placement (prev-line), multiline string re-indentation, trailing commas in multi-element listsswiftTestingTestCaseNames(e.g.func testPolymorphicEnumValue()→func `polymorphic enum value`())The
.swiftformat/.swiftlint.ymlconfiguration files themselves are intentionally not part of this PR.Manual accompaniments (kept the build green)
CodingUserInfoKey.resilientDecodingErrorReporteris written as: CodingUserInfoKey = .init(...)!— thepropertyTypesrule miscompiles the multiline= CodingUserInfoKey(...)!form into a tuple (SwiftFormat 0.62.1 bug). The.initform is stable under re-runs.@DefaultCodabletest doubles are wrapped inswiftformat:disable propertyTypesregions — an explicit type annotation breaks the wrapper's generic parameter inference.Verification
swiftformat .is idempotent on the final tree.swift testpasses in debug (303) and release (295) configurations.Notes
mainafter it merges. Formatting only — no behavior changes beyond the two accompaniments above.https://claude.ai/code/session_017kn3Hf2khxiFy1TqimTGx9