Proguard rules for client library
Open
Nobody has claimed this yet.
Client library
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
The client library has fields that are considered "unused" by proguard, for example when accessed through reflection only.
We need to make sure that proper proguard rules are in place in case the app using the client library uses proguard.
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
No file, test, or entry point is named in the issue. Start by locating the client library's ProGuard configuration and the fields accessed through reflection, then determine which rules are needed. Done means apps using ProGuard retain the required client-library fields without warnings or broken reflective access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100