Samuel Lampa
Samuel Lampa
Right now, to create a new process, you have to give it a name, which sometimes takes focus away from the actuall shell command. Also, the method name `wf.NewProc` is...
Right now, to define a process with an output path pattern, one has to do this in two steps: ```go proc := wf.NewProc("proc", "echo hi > {o:hi}") proc.SetOut("hi", "hi.txt") ```...
Sometimes one wants to use parameter values derived from input filenames etc. Currently one has to choose between two options, e.g: ```go p := wf.NewProc("p", "cmd --some-flag {i:someinput|basename}") ``` ......
Just realized something that would help a lot for some nasty corner cases when writing workflows: Ability to generate commandlines using a Go func, that takes the current task as...
Go best practices recommendations (such as those in [this](https://www.youtube.com/watch?v=29LLRKIL_TI) and [this](https://www.youtube.com/watch?v=yeetIgNeIkc) talk) suggest to use small interfaces with as little as one method, as this often allows to be more...
When receiving input files in a stream to a process, we often need to make use of some context information from each IP, based on the parameters used during the...
Add a new method: ```go proc.SetPathAuditHashed(portName string, prefix string, suffix string) ``` ... which will create a SHA1(?) hash the port name plus all the command, parameters, and upstream commands...