Allow automatically using `.swiftlint.yaml`
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
- I've Updated SwiftLint to the latest version.
- I've searched for existing GitHub issues.
Feature or Enhancement Proposal
Allow automatically using .swiftlint.yaml in addition to .swiftlint.yml (note the different extensions).
I don't care which one is selected over the other if both exist, it would just be nice to be able to have all my YAML files use the same extension (without having to manually reference config files in command line), but some tools automatically use only .yml while some others automatically use only .yaml.
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 locating SwiftLint's automatic configuration-file discovery entry point and the existing handling for .swiftlint.yml. Verify how .swiftlint.yaml should be selected when present, including the case where both files exist, and confirm completion with the relevant configuration-loading tests or command-line behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100