leancodepl / leancodepl/flutter_corelibrary
Rename `use_design_system_item` to something more accurate
Open
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 89
- Forks
- 12
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 2
Description
I think the name of the use_design_system_item lint rule is too specific for what it is actually capable of. It can be used for classes that are not related to design system (though I agree it's the most common use case, and the migration cost probably outweights the (lack of) benefits).
Contributor guide
No contributing guide indexed for this repository
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 the definition and usages of use_design_system_item in the lint rules. Review what classes the rule supports and settle on an accurate replacement name; done means the rule and its references use the agreed name without changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100