kotlinova

Offers a set of utility classes focusing on coroutines, featuring modules for core functionality, UI composition, Gradle integration, navigation, and Retrofit support. Utilizes semantic versioning for updates.

Android JVMJVM
GitHub stars7
Authorsinovait
Open issues0
LicenseMIT License
Creation datealmost 6 years ago

Last activityabout 13 hours ago
Latest release4.0.0-alpha15 (about 18 hours ago)

KOTLINOVA

An opinionated set of common utility classes for Kotlin projects, primarily based on Kotlin coroutines.

Modules

Core

Compose

Gradle

Versioning

This library uses Semantic Versioning. Version number is updated automatically whenever new release is built.

When updating, it is recommended that you check out releases first to see the changes, especially if there was major version change.

Contributing

To contribute to this set of libraries:

  1. Checkout master
  2. Create new branch for your contribution
  3. Commit your work. While commiting, use conventional commits. Scope tag should be the name of the module you are updating.
  4. Try to avoid breaking changes, but if it cannot be avoided, you must put BREAKING CHANGE in the footer of the commit mesasage and explain the change.
  5. Create merge request
  6. When your PR is merged, new release will be generated automatically
Android JVMJVM
GitHub stars7
Authorsinovait
Open issues0
LicenseMIT License
Creation datealmost 6 years ago

Last activityabout 13 hours ago
Latest release4.0.0-alpha15 (about 18 hours ago)

KOTLINOVA

An opinionated set of common utility classes for Kotlin projects, primarily based on Kotlin coroutines.

Modules

Core

Compose

Gradle

Versioning

This library uses Semantic Versioning. Version number is updated automatically whenever new release is built.

When updating, it is recommended that you check out releases first to see the changes, especially if there was major version change.

Contributing

To contribute to this set of libraries:

  1. Checkout master
  2. Create new branch for your contribution
  3. Commit your work. While commiting, use conventional commits. Scope tag should be the name of the module you are updating.
  4. Try to avoid breaking changes, but if it cannot be avoided, you must put BREAKING CHANGE in the footer of the commit mesasage and explain the change.
  5. Create merge request
  6. When your PR is merged, new release will be generated automatically
Survey iconComplete survey to improve klibs.io ↗
Let’s go