Rc 1.1.0 (#1342)

* polish news

* community.rstudio -> forum.posit

* devtools::build_readme()

* remove Remotes

* update news

* make recipes_ptype() return NULL for old recipes

* run revdepcheck

* add skip_on_cran

* version bump

* "Please provide package anchors for all Rd \link{} targets not in the package itself and the base packages."

---------

Co-authored-by: ‘topepo’ <‘[email protected]’>

Author: EmilHvitfeldt

DESCRIPTION

@@ -1,6 +1,6 @@
 Package: recipes
 Title: Preprocessing and Feature Engineering Steps for Modeling
-Version: 1.0.10.9000
+Version: 1.1.0
 Authors@R: c(
     person("Max", "Kuhn", , "[email protected]", role = c("aut", "cre")),
     person("Hadley", "Wickham", , "[email protected]", role = "aut"),
@@ -26,7 +26,7 @@ Imports:
     generics (>= 0.1.2),
     glue,
     gower,
-    hardhat (>= 1.3.1.9000),
+    hardhat (>= 1.4.0),
     ipred (>= 0.9-12),
     lifecycle (>= 1.0.3),
     lubridate (>= 1.8.0),
@@ -71,5 +71,3 @@ Config/testthat/edition: 3
 Encoding: UTF-8
 Roxygen: list(markdown = TRUE)
 RoxygenNote: 7.3.1
-Remotes: 
-    tidymodels/hardhat

NEWS.md

@@ -1,46 +1,54 @@
-# recipes (development version)
+# recipes 1.1.0
 
-* New `extract_fit_time()` method has been added that returns the time it took to train the recipe. (#1071)
+## Improvements
 
-* `step_spline_b()`, `step_spline_convex()`, `step_spline_monotone()`, and `step_spline_nonnegative()` now throws informative errors if the`degree`, `deg_free`, and `complete_set` arguments causes an error. (#1170)
+* Improved error message for misspelled argument in step functions. (#1318)
 
-* Developer helper function `recipes_ptype()` has been added, returning expected input data for `prep()` and `bake()` for a given recipe object. (#1329)
+* `recipe()` can now take data.frames with list-columns or sf data.frames as input to `data`. (#1283)
 
-* Developer helper function `recipes_ptype_validate()` has been added, to validate new data is compatible with recipe ptype. (#793)
+* `recipe()` will now show better error when columns are misspelled in formula (#1283).
 
-* The `prefix` argument of `step_dummy_multi_choice()` is not properly documented. (#1298)
+* `add_role()` now errors if a column would simultaneously have roles `"outcome"` and `"predictor"`. (#935)
 
-* `step_dummy()` now gives an informative error on attempt to generate too many columns to fit in memory. (#828)
+* `prep()` will now error if the ptype of the data doesn't match which was used to define the recipe. (#793)
 
-* `NA` levels in factors aren't dropped when passed to `recipe()`. (#1291)
+* Added more documentation in `?selections` about how `tidyselect::everything()` works in recipes. (#1259)
 
-* `recipe()` no longer crashes when given long formula expression (#1283).
+* New `extract_fit_time()` method has been added that returns the time it took to train the recipe. (#1071)
 
-* `step_interact()` now gives better error if `terms` isn't a formula. (#1299)
+* `step_spline_b()`, `step_spline_convex()`, `step_spline_monotone()`, and `step_spline_nonnegative()` now throws informative errors if the`degree`, `deg_free`, and `complete_set` arguments causes an error. (#1170)
 
-* `recipe()` will now show better error when columns are misspelled in formula (#1283).
+* `step_mutate()` gained `.pkgs` argument to specify what packages need to be loaded for step to work. (#1282)
 
-* Fixed bug in `step_ns()` and `step_bs()` where `knots` field in `options` argument wasn't correctly used. (#1297)
+* `step_interact()` now gives better error if `terms` isn't a formula. (#1299)
 
-* `add_role()` now errors if a column would simultaneously have roles `"outcome"` and `"predictor"`. (#935)
+* The `prefix` argument of `step_dummy_multi_choice()` is now properly documented. (#1298)
 
 * Significant speedup in `step_dummy()` when applied to many columns. (#1305)
 
-* Bug fixed in `step_interact()` where long formulas were used. (#1231, #1289)
-
-* `recipe()` can now take data.frames with list-columns or sf data.frames as input to `data`. (#1283)
+* `step_dummy()` now gives an informative error on attempt to generate too many columns to fit in memory. (#828)
 
 * `step_dummy()` and `step_unknown()` now throw more informative warnings for unseen levels. (#450)
 
 * `step_dummy()` now throws more informative warnings for `NA` values. (#450)
 
+## Bug Fixes
+
+* `NA` levels in factors aren't dropped when passed to `recipe()`. (#1291)
+
+* `recipe()` no longer crashes when given long formula expression (#1283).
+
+* Fixed bug in `step_ns()` and `step_bs()` where `knots` field in `options` argument wasn't correctly used. (#1297)
+
+* Bug fixed in `step_interact()` where long formulas were used. (#1231, #1289)
+
 * Fixed documentation mistake where default value of `keep_original_cols` argument were wrong. (#1314)
 
-* `step_mutate()` gained `.pkgs` argument to specify what packages need to be loaded for step to work. (#1282)
+## Developer
 
-* Added more documentation in `?selections` about how `tidyselect::everything()` works in recipes. (#1259)
+* Developer helper function `recipes_ptype()` has been added, returning expected input data for `prep()` and `bake()` for a given recipe object. (#1329)
 
-* Improved error message for misspelled argument in step functions. (#1318)
+* Developer helper function `recipes_ptype_validate()` has been added, to validate new data is compatible with recipe ptype. (#793)
 
 * Developer helper functions `recipes_names_predictors()` and `recipes_names_outcomes()` have been added to aid variable selection in steps. (#1026)
 

R/ptype.R

@@ -40,6 +40,8 @@
 #' with `update_role_requirements()`, and `recipes_ptype()` respects those 
 #' changes.
 #' 
+#' `recipes_ptype()` returns `NULL` on recipes created prior to version 1.1.0.
+#' 
 #' Note that the order of the columns aren't guaranteed to align with
 #' `data_ptype` as the data internally is ordered according to roles.
 #' 
@@ -84,13 +86,9 @@
 recipes_ptype <- function(x, ..., stage = "prep") {
   check_dots_empty0(...)
 
+  # recipe created prior to 1.1.0
   if (is.null(x$ptype)) {
-   cli::cli_abort(
-      c(
-        x = "Doesn't work on recipes created prior to version 1.1.0.",
-        i = "Please recreate recipe."
-      )
-    )
+    return(NULL)
   }
 
   ptype <- x$ptype
@@ -112,6 +110,15 @@ recipes_ptype <- function(x, ..., stage = "prep") {
   ptype
 }
 
+
+long_function_name <- function(x,
+                               ...,
+                               verbose = FALSE) {
+  x
+}
+
+
+
 #' Validate prototype of recipe object
 #'
 #' This helper function validates a dataframe against the ptype of a recipe.
@@ -143,6 +150,12 @@ recipes_ptype_validate <- function(x,
                                    stage = "prep", 
                                    call = rlang::caller_env()) {
   old_ptype <- recipes_ptype(x, stage = stage)
+
+  # recipe created prior to 1.1.0
+  if (is.null(old_ptype)) {
+    return(invisible())
+  }
+
   col_names <- names(old_ptype)
 
   new_ptype <- vctrs::vec_ptype(new_data)

R/recipe.R

@@ -596,7 +596,7 @@ bake <- function(object, ...) {
 #' @param ... One or more selector functions to choose which variables will be
 #'   returned by the function. See [selections()] for more details.
 #'   If no selectors are given, the default is to use
-#'   [everything()].
+#'   [dplyr::everything()].
 #' @param composition Either "tibble", "matrix", "data.frame", or
 #'  "dgCMatrix" for the format of the processed data set. Note that
 #'  all computations during the baking process are done in a

README.Rmd

@@ -54,7 +54,7 @@ pak::pak("tidymodels/recipes")
 
 ## Contributing
 
-- For questions and discussions about tidymodels packages, modeling, and machine learning, please [post on RStudio Community](https://community.rstudio.com/c/ml/15).
+- For questions and discussions about tidymodels packages, modeling, and machine learning, please [post on RStudio Community](https://forum.posit.co/c/ml/15).
 
 - If you think you have encountered a bug, please [submit an issue](https://github.com/tidymodels/recipes/issues).
 

README.md

@@ -57,18 +57,18 @@ pak::pak("tidymodels/recipes")
 
 ## Contributing
 
--   For questions and discussions about tidymodels packages, modeling,
-    and machine learning, please [post on RStudio
-    Community](https://community.rstudio.com/c/ml/15).
+- For questions and discussions about tidymodels packages, modeling, and
+  machine learning, please [post on RStudio
+  Community](https://forum.posit.co/c/ml/15).
 
--   If you think you have encountered a bug, please [submit an
-    issue](https://github.com/tidymodels/recipes/issues).
+- If you think you have encountered a bug, please [submit an
+  issue](https://github.com/tidymodels/recipes/issues).
 
--   Either way, learn how to create and share a
-    [reprex](https://reprex.tidyverse.org/articles/articles/learn-reprex.html)
-    (a minimal, reproducible example), to clearly communicate about your
-    code.
+- Either way, learn how to create and share a
+  [reprex](https://reprex.tidyverse.org/articles/articles/learn-reprex.html)
+  (a minimal, reproducible example), to clearly communicate about your
+  code.
 
--   Check out further details on [contributing guidelines for tidymodels
-    packages](https://www.tidymodels.org/contribute/) and [how to get
-    help](https://www.tidymodels.org/help/).
+- Check out further details on [contributing guidelines for tidymodels
+  packages](https://www.tidymodels.org/contribute/) and [how to get
+  help](https://www.tidymodels.org/help/).