Folks, what's your biggest pain point or wish rega...

# github-workflows-kt

[Piotr Krzemiński]

Folks, what's your biggest pain point or wish regarding the library? I want to align my priorities with your take on it :) and make sure everything is tracked as an issue in GitHub

[jmfayard]

The coolest feature I would add is to haver the script-generator be a web tool instead of something you have to run locally in a strange way. That could be a ktor server that embeds the library and the code from the script-generator module. That would improve the onboarding experience. That doesn’t require change in the library though.

[Big Chungus]

Doesn't even need a server if you port generator logic to kmp and export it to js.

[Piotr Krzemiński]

Yeah, I like the idea and thought about it as well. My first thought was that it would cost some money to host a JVM app. Then I thought about rewriting the generator to Kotlin/JS to make a SPA hostable for free, but e. g. Kotlin Poet is JVM-only. Still, worth having an issue for it to keep the discussion going and gather interest - would you create it please @jmfayard?
(@Big Chungus just saw your previous message, a Slack glitch?)

[jmfayard]

I’ve thought about an alternative: a GitHub action you run once, which produces the kotlin scripts, run them, remove itself and commit everything.
Any preference from a user perspective?

[Piotr Krzemiński]

https://github.com/krzema12/github-workflows-kt/issues/571

[Piotr Krzemiński]

(made the title ☝️ more generic already)

[Piotr Krzemiński]

@jmfayard nice idea! It does have some drawbacks like challenging error handling, but the general idea is tempting because it requires no extra cost of rewrite and hosting

[Piotr Krzemiński]

FTR, I would see it as a separate repo

[jmfayard]

FYI I’m in a career change, it would be challenging to find the time to do it

[Piotr Krzemiński]

Any other ideas/complaints about the DSL itself? 😉 Some missing crucial features, action wrappers?