ChuckerTeam / ChuckerTeam/chucker
One variant for Chucker instead of two (library & library-no-op)
- Dominant language
- Kotlin
- Stars
- 4.6k
- Forks
- 463
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 18
Description
## :warning: Is your feature request related to a problem? Please describe
It is a request to make chucker has only one variant and can be defined in one line. Two lines/variants for Chucker is really a headache if your project is modularized. Also if you use chucker with a library you will have to make the library has the same variants as chucker to avoid class/resource duplications.
## :raising_hand: Do you want to develop this feature yourself?
- [x] Yes
- [ ] No
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named in the issue. Start by locating the Android/Gradle variant configuration and mapping the library and library-no-op artifacts; done means a modularized project can declare one Chucker variant without matching project variants or duplicate classes and resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100