Kirill Müller
Kirill Müller
Record how long each target takes to run, and print this information before building.
Multiple includes of the same `.yml` currently gives `All target names must be unique`, this seems unnecessary. Example: ``` yml # base.yml targets: test: command: quote(TRUE) # a.yml include: -...
In my project, I have a `RATE` parameter (set by a function) which controls if I'm working with the full dataset or only with a small sample. Many other targets...
Would you consider supporting ``` r targets: : some_r_func(deps) ``` as a shorthand for ``` r targets: : command: some_r_func(deps) ``` ? If I understand YAML correctly, this only works...
If a .yml includes another file, the `sources` in that file should be run first. Currently, it seems that "own" sources are run before "included" sources. Use case: a "base"...
and not in one big blob. Can we also include messages for `correct = TRUE` answers that were not ticked? In the example below I'm missing the message e.g. from...
- highlight grouping columns - use different color for groups - ...
- No row names - Read-only - Significant digits
It's sufficient to pass the SQL and the connection parameters; the latter may be more troublesome. It's worth the effort to extend DBI to support serialization and deserialization of connections.
above/below the widget: dimensions, grouping, expression, ...