Last chance! 50% off unlimited learning
Sale ends in
Should the deactivation of one or more validation steps be necessary after
creation of the validation plan for an agent, the deactivate_steps()
function will be helpful for that. This has the same effect as using the
active = FALSE
option (active
is an argument in all validation functions)
for the selected validation steps. Please note that this directly edits the
validation step, wiping out any function that may have been defined for
whether the step should be active or not.
deactivate_steps(agent, i = NULL)
An agent object of class ptblank_agent
.
The validation step number, which is assigned to each validation step in the order of definition.
A ptblank_agent
object.
9-7
For the opposite behavior, use the activate_steps()
function.
Other Object Ops:
activate_steps()
,
remove_read_fn()
,
remove_steps()
,
remove_tbl()
,
set_read_fn()
,
set_tbl()
,
x_read_disk()
,
x_write_disk()
# NOT RUN {
# Create an agent that has the
# `small_table` object as the
# target table, add a few
# validation steps, and then use
# `interrogate()`
agent_1 <-
create_agent(
read_fn = ~ small_table,
tbl_name = "small_table",
label = "An example."
) %>%
col_exists(vars(date)) %>%
col_vals_regex(
vars(b), regex = "[0-9]-[a-z]{3}-[0-9]"
) %>%
interrogate()
# The second validation step has
# is being reconsidered and may
# be either phased out or improved
# upon; in the interim period it
# was decided that the step should
# be deactivated for now
agent_2 <-
agent_1 %>%
deactivate_steps(i = 2) %>%
interrogate()
# }
Run the code above in your browser using DataLab