flow_debug, flow_debugonce

[moodymudskipper]

Use case :

• covr shows me that a portion of my code is not covered in some unexported function fun_unexp
• I have a test, calling an exported function fun_exp, itself calling fun_unexp, that I thought should cover it

How do I browse through fun_unexp ?

• I can flow_run or debug fun_exp, then find the parameter values and run flow_run on fun_unexp with those
• I can run flow_run with browse = TRUE, then run it again once I arrive to funexp call

These are not that nice.

A solution would be a pair of functions similar to debug and debugonce (or just debugonce), OR a parameter to flow_run, naming the function we want to debug.

The latter would probably need the former under the hood.

flow_debug_once would trace the function with :

• a call to untrace so it won't be traced after first call
• return(flow::flow_run(...))

[moodymudskipper]

done

[github-actions[bot]]

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary.