Check Android Lint Warnings
Open
Nobody has claimed this yet.
Feature request
p3-medium
Technical
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
Lint step is executed in CI system over the code to assure correctness.
Currently, lint in CI is working fine but returning a bunch of warnings. We should review this warnings
TASKS
- Research (if needed)
- Create branch feature/feature_name
- Development tasks
- Implement whatever
- ...
- Code review and apply changes requested
- Design test plan
- QA
- Merge branch feature/feature_name into master
PR
- App
- Library (if 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
Start by running the Android Lint step in CI and cataloging the warnings it reports. Review the warning locations and determine which are actionable; done means the warnings have been addressed or explicitly assessed, with the CI lint result verified. The issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- ci-cd, mobile
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100