This message was deleted.
# kotlin-dsl
s
This message was deleted.
f
You want to generate the .json/.yaml to be used by swagger ui, is that what you are asking?
j
The other way around. I have the .json/.yaml, and want to generate the Swagger UI with a Gradle build.
I have a project where I used a particular Gradle plugin, and used the Groovy syntax. I was looking to modernize the build, and am pretty unopinionated as to how, but would like to do it in a “good way.”
v
What hinders you to use that plugin with Kotlin DSL too?
j
Well, I started to translate the syntax (which started a bit challenging, but just because the documentation for the plugin wasn’t in that syntax). I seem to have that configured, and it seems to not be working.
But, rather than spending time debugging the configuration, I’d like to “use a modern plugin and modern use of subprojects and Kotlin,etc.”
I’m less concerned with doing-what-I-did-before and more concerned with doing-things-in-a-good-way.
👌 1
So… nobody has a feeling about what approach might be… a best (better-than-some) practice?
v
I'm simply not sure why using a plugin that does exactly what you want should not be the best practice?
j
So, you’d use the plugin I used before, and attempt to modify the build declaration to use the Kotlin DSL?
(I really don’t care which plugin/mechanism we use. It strains my mind to believe that I’m the first person to try to solve this problem. 😊)
v
Sure, why not? Plugins are not DSL-specific. Granted, some are a bit weird to use in Kotlin DSL if they are too tied to Groovy magic. But then you should probably report to that plugin to improve for Kotlin DSL usage. Latest now that Kotlin DSL is the official default DSL, you have good arguments for that. 🙂