Fork me on GitHub
#babashka
<
2021-08-26
>
imre12:08:26

Does bb tasks have some built-in support to supply command line arg info about available tasks?

solf12:08:30

bb tasks

imre12:08:19

Yep, but that's only task names plus a str doc.

imre12:08:06

What I'm looking for is some declarative way of advertising what args different tasks take

borkdude12:08:52

@U08BJGV6E There is nothing built in for this.

imre13:08:19

cheers, just didn't want to do the work if there was already something!

imre13:08:32

Thank you, I'll check that out

👍 3
plins14:08:51

Im trying to setup some tasks with babashka, and I currently have this

:tasks
 {outdated (do
             (shell "clojure -M:antq -m antq.core")
             (shell "npm outdated"))}
is there a way of printing the output of both of them and execute all of them regardless of the exit status of the first?

borkdude14:08:16

@plins yes, use (shell {:continue true} ...)

thanks3 3
borkdude15:08:27

How does the implementation work?

rwstauner15:08:39

looks like they are just executables, more like the way git works

rwstauner15:08:55

i think what "gh" adds is auto-installation via a repo naming convention

borkdude15:08:33

ah so they just hand off control to the executable and that's it?

borkdude15:08:42

pods work more like RPC

Adam Stokes15:08:52

Yea I think gh is written in go and I've seen some projects that support a plugin system over gRPC but this just looks like it provides a mechanism to download executables and execute them through a gh- prefix

Adam Stokes15:08:46

So not quite the same 😄

borkdude15:08:50

ah yes, I recently stumbled upon that when looking at some mapreduce homework assignment