audit for backticked package names

[simonpcouch]

In many places in parsnip, the package name is written "parsnip" rather than "parsnip" (i.e. there are backticks before and after). Per tidy style, package names don't need backticks.

Here's an example GitHub search:

https://github.com/search?q=repo%3Atidymodels%2Fparsnip+%22%60parsnip%60%22&type=code

Let's search for tidymodels and tidyverse package names and make sure they're not backticked.

The part that makes this a little more tricky than a Find and Replace is knowing when the thing should actually be backticked vs. not. If the text is definitely referencing parsnip as a package, take the backticks away. If there's e.g. a reference to the tune() function rather than the package tune, leave it as is (making sure to include parentheses following function names if needed). Be sure to devtools::document() and/or devtools::build_readme() before putting in the PR!

[topepo]

Some code that will help you run document():

truly_req_pkgs <- c("glmnet", "Cubist", "xrf", "ape", parsnip:::extensions())

pak::pak(truly_req_pkgs, ask = FALSE)

# Before devtools::document()
inst <- purrr::map(rmd_pkgs, ~ library(.x, character.only = TRUE))

[luisDVA]

hi max @topepo ,
Currently in the process of running the documentation for my PR on this. The snippet above helped me install ~140 pkgs but some are still missing when I run document() so I'm installing them manually. In the code above what was rmd_pkgs meant to refer to?

[simonpcouch]

Addressed in #1158. :)

[github-actions]

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.