5 curated breaking changes across major versions of tidyselect. Use this as a migration checklist before bumping dependencies.
Selecting non-column variables with bare names now triggers an informative message suggesting to use `all_of()` instead. Referring to contextual objects with a bare name is brittle because it might be masked by a data frame column. Using `all_of()` is safe (#76). tidyselect now uses vctrs for validating inputs. These changes may reveal programming errors that were previously silent. They may also cause failures if your unit tests make faulty assumptions about the content of error messages create
Out-of-bounds errors are thrown when a name doesn't exist or a location is too large for the input.
Logical vectors now fail properly.
Selected variables now must be unique. It was previously possible to return duplicate selections in some circumstances.
Get this data programmatically \u2014 free, no authentication.
curl https://depscope.dev/api/breaking/cran/tidyselectThe input names can no longer contain `NA` values. Note that we recommend `testthat::verify_output()` for monitoring error messages thrown from packages that you don't control. Unlike `expect_error()`, `verify_output()` does not cause CMD check failures when error messages have changed. See <https://www.tidyverse.org/blog/2019/11/testthat-2-3-0/> for more information.