View source: R/05_flow_debug.R
flow_debug | R Documentation |
These functions are named after the base functions debug()
, undebug()
and
debugonce()
. flow_debug()
will call flow_run()
, with the same additional arguments, on all the following
calls to f()
until flow_undebug()
is called. flow_debugonce()
will only
call flow_run()
on the next call to f()
.
flow_debug( f, prefix = NULL, code = TRUE, narrow = FALSE, truncate = NULL, swap = TRUE, out = NULL, browse = FALSE ) flow_debugonce( f, prefix = NULL, code = TRUE, narrow = FALSE, truncate = NULL, swap = TRUE, out = NULL, browse = FALSE ) flow_undebug(f)
f |
function to debug |
prefix |
prefix to use for special comments in our code used as block headers,
must start with |
code |
Whether to display the code in code blocks or only the header,
to be more compact, if |
narrow |
|
truncate |
maximum number of characters to be printed per line |
swap |
whether to change |
out |
a path to save the diagram to. Special values "html", "htm", "png", "pdf", "jpg" and "jpeg" can be used to export the object to a temp file of the relevant format and open it, if a regular path is used the format will be guessed from the extension. |
browse |
whether to debug step by step (block by block),
can also be a vector of block ids, in this case |
By default, unlike debug()
and debugonce()
, flow_debug()
and
flow_debugonce()
don't trigger a debugger but only draw diagrams, this is
consistent with flow_run()
's defaults. To browse through the code, use
the browse
argument.
These functions return NULL
invisibly (called for side effects)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.