leancodepl / leancodepl/flutter_corelibrary
Add custom linter rule to prevent usage of string literals in widgets
Open
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 89
- Forks
- 12
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 2
Description
When using internalization (e.g. through a package such as i18n), no text placed in the UI should be hardcoded to one language. We could implement a custom linter rule to prevent this from happening.
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 repository's existing lint configuration and any custom analyzer rules related to Flutter widgets. Clarify which string literals count as UI text and how localization is detected; done means the rule reliably flags hardcoded widget text without producing unacceptable false positives.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- internationalization, mobile, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100