Rule Request: Created NSLayoutConstraint from anchor and did nothing with it
Open
Nobody has claimed this yet.
rule-request
- Dominant language
- Swift
- Stars
- 19.7k
- Forks
- 2.3k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 11
Description
I have had UI goofups prolonged by the fact that I created a constraint using an anchor and never did anything with it (such as set isActive = true or assign it to a variable). There should probably be a rule that warns when this happens.
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
The issue names no files, tests, or entry points. Start by locating SwiftLint's existing rule implementations and their tests, then determine how an unused NSLayoutConstraint created from an anchor should be detected; done means the rule warns for the described case without inappropriate warnings.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100