Releases: vknabel/vscode-swiftlint
Releases · vknabel/vscode-swiftlint
v1.8.4
What's Changed
- Bump semver from 5.7.1 to 5.7.2 by @dependabot in #66
- Make default swiftlint.path value cross-platform by @tristanlabelle in #72
- Fix stdout/stderr buffering on Windows by @tristanlabelle in #73
- Update build.yaml by @vknabel in #91
- Fixed "no lintable files found" error when navigating to Swift interface files by @FelixLisczyk in #85
- Fixed "no lintable files found" error when adding files to Cursor AI Chat by @FelixLisczyk in #90
New Contributors
- @tristanlabelle made their first contribution in #72
- @vknabel made their first contribution in #91
- @FelixLisczyk made their first contribution in #85
Full Changelog: 1.8.1...v1.8.4
1.8.4-beta.3
Full Changelog: 1.8.4-beta.2...1.8.4-beta.3
Windows different shell execution
Full Changelog: 1.8.4-beta.1...1.8.4-beta.2
Windows default path Pre-release
1.8.4-beta.1 1.8.4-beta.1
Windows default path
- fix: default swiftlint.path value is invalid on Windows #67
1.8.0
- Added:
vscode-swiftlint.path
can now be an array of strings and defaults to[/usr/bin/env, swift-format]
vknabel/vscode-apple-swift-format#17
1.7.3
--format and building
Autocorrect and fix
- New commands to fix autocorrect workspace and file issues
swiftlint.fixWorkspace
andswiftlint.fixDocument
#40
To automatically fix all issues within a document on save, add the following to your .vscode/settings.json
:
{
"editor.codeActionsOnSave": {
"source.fixAll": true
}
}
Full Changelog: 1.4.6...v1.5.0
Banned some configs from workspace settings
Fixes vulnerability which allowed malicous workspaces to execute code when opened by providing. Now the vulnerable configs cannot be overrided in workspaces anymore: swiftlint.path
. Reported by @Ry0taK.