Replace different variables and functions to set a specific property of the chart in different units with extension properties on numbers like used in Jetpack Compose (source code).

Example: 40.dp 12.px

Update Android Gradle Plugin to version 7.0.0, and Gradle to version 7.1.1, and Kotlin to version 1.5.21 and also update the Java compile version to 11

see https://developer.android.com/studio/releases/gradle-plugin?buildsystem=cmake#java-11

Include issue number (if any) and commit hashes that a feature, bug, etc. refers to in the end of that changelog entry, like this:

New features

• Feature 1 (#0, a1b2c3d, ...)

Configure CI/CD for the library either with GitHub or with Travis CI (other tutorial 1, other tutorial 2).

• [x] Update the ciManagement in publishing block of the build script
• [x] Create and publish the test app APK in the GitHub release
• [x] Add or update the badge for CI/CD in the main README
• [x] Disable force push to prod branch in IntelliJ
• [x] Disable force push to prod branch in GitHub

Implement legends for the chart.

• [x] legend, legendSize, icon, iconHeight, iconTint, iconTransparency, iconMargin, percent, percentSize, percentMargin
• [x] Legends margin from the pie
• [x] Margin between each legend
• [x] Legends title
• [x] Legend title margin
• [x] Margin between lines if legends are so many that they constitute multiple lines
• [x] Custom legend icon
• [x] Box for legends
  • [x] Background color
  • [x] Box padding
  • [x] Box border
    • [x] Border thickness
    • [x] Border color
    • [x] Border shape (solid, dashed, ...)
    • [x] Border corner radius
• [x] Property for aligning legend box in the view (center, start, end)

At the very least these legends should be supported:

• horizontal top
• horizontal bottom
• vertical left/start
• vertical right/end
• vertical in-hole

Use a library to add screenshot tests as acceptance tests to ensure the final appearance of the chart is appropriate.

The two libraries defined below do not support running screenshot tests on Windows 10. Use them when/if they support Windows 10 (though it might be late to this because most of the library features will have been implemented by that time and writing tests afterwards may not be so useful). Refer to this issue for shot and this section for screenshot-tests-for-android to see if they have started to support Windows 10 or not.

See this (note how it saves the images and compares them. Also note that it reads screenshots from the assets directory).

Possible libraries:

• https://medium.com/stepstone-tech/how-to-capture-screenshots-for-failed-ui-tests-9927eea6e1e4
• https://github.com/square/spoon
• https://github.com/rtyley/android-screenshot-lib
• https://github.com/Karumi/Shot (example usage in a library could be found in samplelibrary subproject here)
• https://github.com/facebook/screenshot-tests-for-android (https://jobandtalent.engineering/screenshot-testing-on-android-88da6c004cf0)

Another solution:

• https://proandroiddev.com/easy-ui-and-screenshot-testing-on-android-2b138f6d1eb8

Can we use "Emulator Snapshots for test failures" available in newer versions of Android Studio?

In unit tests that compare floating point numbers, update the assertions to compare with 0.01 precision instead of current 1.

This is because current comparisons may give false negative results, that is, pass when they should have failed.

The javadoc.jar artifact has no javadoc in it. For example, this javadoc for version 0.4.0 of the library.

See this post and this post and this page and also dokka homepage for setting up kdoc in Android.

Important

If the docs cannot be generated offline, add this block of code to the build script:

val dokka by tasks.getting(org.jetbrains.dokka.gradle.DokkaTask::class)
dokka.configure<org.jetbrains.dokka.gradle.DokkaTask> {
    dokkaSourceSets {
        named("main") {
            noAndroidSdkLink.set(false)
        }
    }
}

See this and this and https://github.com/Kotlin/dokka/issues/1706 for more information about the noAndroidSdkLink property.

Add ability to specify a label/icon in the center of the chart.

The chart hole is not modified and may overlap with the center label/icon (because the user may want that behavior).

It is up to the user to make sure the hole is big enough to accommodate the center label/icon, if he wants no overlap.

For each new version of the library, publish its KDoc files (i.e. content of the javadoc.jar) to the website (Git branch on GitHub) automatically (using a CI in GitHub Actions).

NOTE

Dokka supports Versioning plugin as stated in its website which aims to "provide users with ability to create a versioned documentation. Therefore, users of the documentation can view different versions of the documentation by going to the main page and change versions."

https://github.com/data2viz/data2viz https://github.com/grafana/grafana https://github.com/apache/superset https://github.com/JetBrains/lets-plot https://github.com/AAChartModel/AAChartCore-Kotlin