Update fails on a rich version declaration

[eugene-krivobokov]

Environment:

nl.littlerobots.version-catalog-update: 0.2.1
com.github.ben-manes.versions: 0.39.0
Gradle: 7.3.2

libs.versions.toml:

[versions]
kotlinCoroutines = { strictly = "1.5.2-native-mt" }

[libraries]
kotlin-coroutines = { module = "org.jetbrains.kotlinx:kotlinx-coroutines-core", version.ref = "kotlinCoroutines" }
kotlin-coroutinesAndroid = { module = "org.jetbrains.kotlinx:kotlinx-coroutines-android", version.ref = "kotlinCoroutines" }

Scenario:

./gradlew versionCatalogUpdate --no-configuration-cache

Unexpected result:

Caused by: java.lang.IllegalStateException: Expected class java.lang.String for key kotlinCoroutines, but was class java.util.LinkedHashMap	
at nl.littlerobots.vcu.VersionCatalogParser.parse(VersionCatalogParser.kt:131)	
at nl.littlerobots.vcu.plugin.VersionCatalogUpdateTask.updateCatalog(VersionCatalogUpdateTask.kt:83)

This format is only the one of possible: toml-dependencies-format

Expected behavior

It's not obvious how to make a decision in different combinations of a rich version.
There're higher chances that such customizations are because of some workarounds.
Maybe It's safer to start skipping them and warn users about this decision.

[hvisser]

Thanks for reporting, you're right I missed that a version could be a rich declaration in the version block too. There is some handling for library declarations but I think in that case the library is left alone without any updates, like you suggest. After checking; there is handling for it in the version parser, but the updating the catalog isn't handled correctly either, so that needs to be fixed too then 😅

[hvisser]

While there's no automatic update on version definitions with a condition, a message is logged when updates are available for dependencies using a condition.