You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0b71252
Browse filesBrowse the repository at this point in the historyBrowse files
CI: format and syntax checks instead of build (#10)
* build: add a swift-format configuration
4-space indentation and a 120-column limit, matching what the sources
already use. Without a config swift-format defaults to 2 spaces and
reports 3301 Indentation warnings across the tree, which would bury the
warnings that matter.
Also renames the LSP SymbolKind.null_ case to nullValue: the trailing
underscore is a keyword workaround and trips AlwaysUseLowerCamelCase.
* style: apply swift-format across Sources and Tests
Mechanical reformat only; no behaviour change. Build and the 35 tests
pass unchanged.
Fixes two spots the formatter flagged as more than whitespace:
- FileExplorerView's context menu set two properties on one line
separated by semicolons, now one statement per line
- import blocks are now lexicographically ordered
swift-format lint --strict reports zero warnings afterwards.
* ci: check formatting and syntax instead of building
Build and test cannot run on a hosted runner: the package declares
swift-tools-version 6.4, CodeEditSourceEditor 0.15 needs SwiftPM 6.4 to
generate its resource bundles, and runners top out at 6.3.3. Lowering the
manifest to 6.3 clears SwiftPM but then fails inside a dependency --
CodeEditSymbols 0.2.3 declares no resources, so SwiftPM 6.3 does not emit
Bundle.module. The toolchain is the constraint, not this package.
Replace the non-blocking build job with two checks that do work anywhere:
- Format: swift-format lint --strict, then format --in-place and fail if
git sees a change. swift-format ships inside the Xcode toolchain, so it
is present regardless of the Swift version.
- Syntax: swiftc -parse on every file. Parsing does not resolve the
dependency graph, so it needs no SwiftPM. This catches malformed source
but not type errors.
Neither substitutes for a build; build and test stay a local and
release-time gate until a runner ships 6.4. The comment at the bottom of
the file says so, and names what to add when that happens.
---------
Co-authored-by: yan <yan@localhost>
0 commit comments