matteocrippa / matteocrippa/karamba
[Request Feature] Separate features into modules.
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 51
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Kotlin extensions is huge, I think author should separate extensions by modules.
For examples:
- core module, include generic class type helpers: 'com.github.matteocrippa:karamba-core:1.2.0'
- image module, include bitmap, drawable, images helpers: 'com.github.matteocrippa:karamba-image:1.2.0'
- localization module, include currency, locale, country,... helpers: 'com.github.matteocrippa:karamba-localization:1.2.0'
- dialogs module, include alert, toast, bottomsheet helpers: 'com.github.matteocrippa:karamba-dialogs:1.2.0'
...
Core android (ktx) already do that, reference modules of material-dialogs: https://github.com/afollestad/material-dialogs
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 files, tests, or entry points are identified. Start by mapping the existing Kotlin extension layout and build modules, then compare the proposed core, image, localization, and dialogs boundaries with material-dialogs. Done would require an agreed module structure and a clear migration plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100