comparative flow_run()s ?

[moodymudskipper]

Not sure about the api but we often have a bug for a given value that we wish to compare with a succesfull case.

In those cases flow_run will show similar diagrams and the differences might explain the errors.

It could even be recursive and fo investigate the differences deeper in the call, going into the call that makes both runs diverge.

[moodymudskipper]

The recursive one is tricky but the simple one might not be all that hard.

• flow_compare_runs(call1, call2, ...) builds first the data for both runs
• data is combined, observations with a dashed line one side and a full line on the other are flagged and get a full line of a specific colour, e.g. resp green and red
• display chart

We might either return invisible NULL or invisible list of outputs, but invisible(NULL) is probably fine

[moodymudskipper]

let's try this as the standout feature of 0.1.1, seems like a low hanging fruit

[moodymudskipper]

Ultimately we should really be able to compare run across git branches, or staged vs unstaged, or commit vs commit. It would greatly help with the "it worked before what did I do" type of situations.

[moodymudskipper]

done in last CRAN version, to compare commits or versions we need a mature {pkg} I think https://github.com/moodymudskipper/pkg