You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
Coverage of enum classes is incorrectly calculated when using kover in Kotlin 2.0.
Errors
If present, stacktraces or files from build/kover/errors directory
N/A
Expected behavior
A clear and concise description of what you expected to happen.
Incorrect display of the last ‘}’ string in the Enum class
Kotlin 1.9.23
Kotlin 2.0.0
Reproducer
A link to your project, if it is open source. Otherwise, please try to reproduce the problem on a small project.
If this is not feasible, give an example of the code on which the problem manifests itself.
Reports
If applicable, report files or screenshots.
Kotlin 1.9.23
Kotlin 2.0.0
Environment
Kover Gradle Plugin version: 0.8.0
Gradle version: 8.7
Kotlin project type: Kotlin/JVM (Spring boot)
Coverage Toolset (if customized in build script): Kover
Other context important for this bug: Windows 11
The text was updated successfully, but these errors were encountered:
@zuevmaxim ,
new enums have additional getEntries method and code in <clinit> (private static final EnumEntries $ENTRIES = EnumEntriesKt.enumEntries((Enum[])$VALUES);)
Describe the bug
A clear and concise description of what the bug is.
Coverage of enum classes is incorrectly calculated when using kover in Kotlin 2.0.
Errors
If present, stacktraces or files from
build/kover/errors
directoryN/A
Expected behavior
A clear and concise description of what you expected to happen.
Incorrect display of the last ‘}’ string in the Enum class
Reproducer
A link to your project, if it is open source. Otherwise, please try to reproduce the problem on a small project.
If this is not feasible, give an example of the code on which the problem manifests itself.
Reports
If applicable, report files or screenshots.
Environment
The text was updated successfully, but these errors were encountered: