Emil Hvitfeldt

I'm closing this issue in favor of https://github.com/tidymodels/recipes/issues/1305

same with `printer()`

same for `prepare()`

for `ellipse_check()` it is a little more involved, since it more of a "you shouldn't need to use this function"

If this is done well, we can add a `prefix()` applier helper function

```r library(tidyverse) library(recipes) steps stringr::str_subset("^step_") |> stringr::str_subset("_new$", negate = TRUE) |> setdiff("step_testthat_helper") get_arg str_remove("\\} *\\\\item") } dots mutate(doc = map_chr(name, get_doc)) |> filter(str_detect(name, "impute$", negate = TRUE)) dots |> count(doc)...

Hello @zhaoliang0302, I have been thinking about such steps for a while, do you know of any existing methods that would work to do such an opperation?

We are testing all our steps here: https://github.com/tidymodels/recipes/blob/main/tests/testthat/test-skipping.R#L37-L63 but it would be better if the check could be implemented fast in `prep.recipe()`

Some of these CI failure also appear on dev branch

I'm working on a package that handles timed data in recipes. So I think this type of feature would be better served as `step_time_lag()` that will be added to that...