Rule Request: mandatory_protocol_for_viewcontroller
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
New Issue Checklist
- Updated SwiftLint to the latest version
- I searched for existing GitHub issues
New rule request
- This rule will restrict user to inherit protocol class in UIViewController. this will be help full to mandate Clean swift Viper architecture. also for those new controllers where some predefined set off constraint need to perform.
- i.e. If I have not inherited one protocol in my UIViewController then it will notify user to inherit mandatory protocol for this class.
- Yes this rule will be configurable. like it will be only apply to UIViewController only or else class as well.
- default this rule is disable. because not in every project this is needed.
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
No source file or test is named. Start by reviewing SwiftLint's existing rule and configuration entry points, then determine how to detect UIViewController subclasses, require a configurable protocol, and keep the rule disabled by default; done means the rule reports missing protocol conformance only when enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100