Add Kover configuration to kmp-lib convention plugin #110
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Ensures Kover API compatibility across all convention plugins by adding missing configuration to
kmp-lib.gradle.kts.Motivation and Context
The
kmp-libconvention plugin applied Kover but lacked configuration, unlikeandroid-libandjava-libwhich use centralizedKoverConfig. This inconsistency could cause issues with the Kover API migration fromkoverReporttokover.reports.Type of Change
How Has This Been Tested?
Screenshots (if applicable)
N/A
Checklist
Additional Context
Changes:
KoverProjectExtensionimport tokmp-lib.gradle.ktsextensions.configure<KoverProjectExtension>("kover", KoverConfig(layout).configure)Affected modules:
:libraries:smokes:domain:features:chatbot:domain:features:home:domainAll three convention plugins (
android-lib,java-lib,kmp-lib) now follow identical Kover configuration pattern.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.