We welcome contributions and are happy to discuss ideas, answer questions, and help you get started.
Before opening a pull request, please open an issue or start a discussion with the maintainers. This helps us:
- Ensure the change aligns with the project's direction
- Avoid duplicate or conflicting work
- Provide guidance on implementation approach
We're friendly and responsive—don't hesitate to reach out!
This repo uses ktlint for formatting.
Please consider adding a pre-commit hook for formatting using
./gradlew addKtlintCheckGitPreCommitHook
Manual formatting is done by invoking
./gradlew ktlintFormat
This repo uses the Kotlin Binary Validator to ensure that changes do not break binary compatibility without us noticing.
The gradle check task on CI will validate against the generated API file.
When doing code changes that do not imply any changes in public API, no additional actions should be performed.
When doing code changes that imply changes in public API, whether it is a new API or adjustments in existing one,
the check task will start to fail.
This requires you to run the gradle apiDump task (on the failing gradle project) manually, the
resulting diff in .api file should be verified: only signatures you expected to change should be changed.
Commit the resulting .api diff along with code changes.