Not pulling in unneeded dependencies is important, especially for libraries. Otherwise buildtimes and app sizes grow unnecessarily.
Compose UI tooling should never end up in a release build, it is only to show previews in Android Studio.
connyduck/unifiedpush-android-distributor:remove-unused-dependencies into main Not pulling in unneeded dependencies is important, especially for libraries. Otherwise buildtimes and app sizes grow unnecessarily.
Compose UI tooling should never end up in a release build, it is only to show previews in Android Studio.
Thank you ! Are you actually using these lib ? I've done it to help maintaining 3 distributors, but the API will often break
Are you actually using these lib ? I've done it to help maintaining 3 distributors, but the API will often break
Not yet! I wouldn't mind a breaking Api, but it would be cool if there was a 1.0.0 release and then strict semantic versioning.
I want to keep it 0-ver to make sure nobody expect any stability from the API, but I can increase minor version every time something break 👍
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?