No way to use `--strict` or `--fix` with the Xcode Build Plugin
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 19.7k
- Forks
- 2.3k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 11
Description
New Issue Checklist
- Updated SwiftLint to the latest version
- I searched for existing GitHub issues
Describe the bug
When using the Xcode Build Plugin to run SwiftLint, it seems like there's no ability to activate many of SwiftLint's command line options, such as --strict or --fix.
My proposed fix to this is to add new configuration options that allow a user to use these options. For example, if strict: true were present in the configuration file, then SwiftLint would run as if invoked by swiftlint --strict.
Complete output when running SwiftLint, including the stack trace and command used
N/A
Environment
- SwiftLint version: 0.50.3
- Installation method used: Xcode Build Plugin
- Paste your configuration file: N/A
- Are you using nested configurations? No
- Which Xcode version are you using (check
xcodebuild -version)? 14.1 - Do you have a sample that shows the issue? N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the Xcode Build Plugin invokes SwiftLint and how command-line options such as --strict and --fix are represented. Compare the plugin's configuration handling with SwiftLint's command-line entry point; done means users can configure the requested options and the plugin applies them consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100