Hello dear users, I am considering adding config o...

# refreshversions

[louiscad]

Hello dear users, I am considering adding config options to refreshVersions, and I'd like your thoughs/feedback on this draft proposal!

https://github.com/jmfayard/refreshVersions/issues/202

[Nikky]

but you have id("de.fayard.refreshVersions") applied on the root project, could you not configure in there? or would that be loaded too late ?

[louiscad]

@Nikky It's not configured that way, it's configured in settings.gradle.kts

[Nikky]

either way i think the kotlin-dsl is better, i'd rather use that and have it break in a obvious way rather than silently do the wrong thing

[louiscad]

Well, since for the .properties approach, I would use namespaced keys, I could warn or break on a per case basis on misconfiguration.

[Nikky]

in kotlin-dsl you could do aliasing and mark them as @Deprecated so migration will work

[Nikky]

does not even need the full replaceWith stuff, as long as it is marked as error and the comment explains what to use instead

[louiscad]

Yes, but it's more cumbersome to maintain, and can break if user migrates while skipping releases (although this can be expected)

[louiscad]

The thing is that any breakage would degrade the IDE experience as the settings script must be correct for the IDE to provide assistance

[louiscad]

That makes looking for the API harder

[Nikky]

well if the .properties file has documentation as comments and would automatically regenerate and mark invalid entries then it could provide similar insights

[louiscad]

Yes

[louiscad]

Hard to pick 😅