Nils Homer
Nils Homer
@tfenne I am wondering if this solves your use case for: https://github.com/fulcrumgenomics/dagr/issues/272 The precedence about where the report is written is: 1. The path specified by `--report`. 2. The output...
@tfenne looking for some feedback. My only regret is having to use a Java enum to expose the strategy options on the command line. Perhaps I could play with `ClassFinder`...
The fixes are described in the second commit message pasted here: Various fixes for usages derived from the `@arg` annotation. Enforce if both 'flag' and 'name' are given in the...
Just putting this here until we need it, but so that I don't forget it exists. I'll try to keep this up-to-date with master.
Currently, any downstream operations on the result of a flatMap requires all tasks depended on by flatMap to be completed successfully before the downstream operations are performed.
Just like we have `EmptyDependable`, I would like an `EmptyTask`, which does nothing (doesn't need to be run). I can then a task that conditionally runs, without having to implement...
We will need to aggregate coverage across modules, and so need to write support for that in mill. Example: https://github.com/lihaoyi/mill/pull/415/files#diff-3cf9da0823659a5cf676dbd815c6f18aR75
At the end of the execution, I want a report that has the following columns: * task name/id/etc. * input/output file * path to file * exists at the end...
- [ ] explain project organization in `build.sbt` now that we are compiling both to JVM and JS. - [ ] fix up all the tests (they broke with my...