This message was deleted.
# plugin-development
s
This message was deleted.
t
Most of my tasks/worker actions these days have a
runBlocking
at the root of the code. Leaving the actual thread management to gradle when appropriate and sometimes leaning on Dispatcher.IO when sending off webhooks etc.
m
My rule of thumb is: no Flow/suspend in the public API of plugins (and generally no Kotlin feature in the public API) because it's a pain for Groovy users. Implementation is fine to use coroutines
💯 1
t
lol my rule of thumb is I don't care about groovy users or people more than 2 or 3 minor versions behind 😄😬
💯 1
😄 1
in my defense most of my gradle these days is work private stuff where I am the core contrib of everything build and CI