Linting should fail when baseline violations are fixed
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Swift
- Stars
- 19.7k
- Forks
- 2.3k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 11
Description
New Issue Checklist
- I've Updated SwiftLint to the latest version.
- I've searched for existing GitHub issues.
Feature or Enhancement Proposal
As with other linter baseline implementations, a fix to a violation that was previously baselined should cause a lint failure that encourages the user to update the baseline. For backwards compatibility, this should probably be a flag, e.g. --strict-baseline or something (feel free to bikeshed).
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 with SwiftLint's existing baseline implementation and compare how other linters handle fixes to baselined violations. Define the backward-compatible strict-baseline flag behavior; done means a fixed baselined violation fails linting and tells users to update the baseline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100