Spring cleaning 🧼 (#31)

* Tidy the DESCRIPTION

* Use styler

* Update snapshots

* Update badges

* Add package doc

* Add RStudio as funder, update CoC

* Update pkgdown

* Add CODEOWNERS

* Back to old snapshot

* No Windows + R 3.6 (cannot install deps)

Author: juliasilge

.github/CODEOWNERS

@@ -0,0 +1,3 @@
+# CODEOWNERS for usemodels
+# https://www.tidyverse.org/development/understudies
+.github/CODEOWNERS @topepo @juliasilge

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,126 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at [email protected]. 
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][https://github.com/mozilla/inclusion].
+
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are available at <https://www.contributor-covenant.org/translations>.
+
+[homepage]: https://www.contributor-covenant.org

.github/workflows/R-CMD-check.yaml

@@ -25,8 +25,6 @@ jobs:
           - {os: macOS-latest,   r: 'release'}
 
           - {os: windows-latest, r: 'release'}
-          # Use 3.6 to trigger usage of RTools35
-          - {os: windows-latest, r: '3.6'}
 
           # Use older ubuntu to maximise backward compatibility
           - {os: ubuntu-18.04,   r: 'devel', http-user-agent: 'release'}

DESCRIPTION

@@ -4,13 +4,16 @@ Version: 0.2.0.9000
 Authors@R: c(
     person("Max", "Kuhn", , "[email protected]", role = c("aut", "cre"),
            comment = c(ORCID = "0000-0003-2402-136X")),
-    person("RStudio", role = "cph")
+    person("RStudio", role = c("cph", "fnd"))
   )
 Description: Code snippets to fit models using the tidymodels framework
     can be easily created for a given data set.
 License: MIT + file LICENSE
-URL: https://usemodels.tidymodels.org/, https://github.com/tidymodels/usemodels
+URL: https://usemodels.tidymodels.org/,
+    https://github.com/tidymodels/usemodels
 BugReports: https://github.com/tidymodels/usemodels/issues
+Depends: 
+    R (>= 3.4)
 Imports: 
     cli,
     clipr,
@@ -25,7 +28,8 @@ Suggests:
     modeldata,
     spelling,
     testthat
-Config/Needs/website: tidyverse/tidytemplate
+Config/Needs/website: 
+    tidyverse/tidytemplate
 Config/testthat/edition: 3
 Encoding: UTF-8
 Language: en-US

R/0_imports.R

@@ -1,3 +1,11 @@
+#' @keywords internal
+"_PACKAGE"
+
+## usethis namespace: start
+## usethis namespace: end
+NULL
+
+# ------------------------------------------------------------------------------
 
 #' @import rlang
 #' @import tune

R/messages.R

@@ -34,4 +34,3 @@ string_to_factor_msg <-
     "For modeling, it is preferred to encode qualitative data as factors",
     "(instead of character)."
   )
-

R/misc.R

@@ -20,7 +20,9 @@ y_lvl <- function(rec) {
   }
   var_roles <- summary(rec)
   y_cols <- var_roles$variable[var_roles$role == "outcome"]
-  y_dat <- rec$template %>% dplyr::select(one_of(y_cols)) %>% dplyr::pull(1)
+  y_dat <- rec$template %>%
+    dplyr::select(one_of(y_cols)) %>%
+    dplyr::pull(1)
   length(levels(y_dat))
 }
 
@@ -89,7 +91,7 @@ add_steps_dummy_vars <- function(base, hot = FALSE, add = FALSE, colors = TRUE)
       add_comment(dummy_hot_msg, add, colors = colors) %>%
       pipe_value(step_dummy(all_nominal_predictors(), one_hot = TRUE))
   } else {
-    base <- base  %>%
+    base <- base %>%
       add_comment(dummy_msg, add, colors = colors) %>%
       pipe_value(step_dummy(all_nominal_predictors()))
   }
@@ -104,8 +106,10 @@ factor_check <- function(base, rec, add, colors = TRUE) {
   var_roles <- summary(rec)
   nominal <- var_roles$variable[var_roles$type == "nominal"]
   is_str <-
-    purrr::map_lgl(rec$template %>% dplyr::select(dplyr::one_of(nominal)),
-                   rlang::is_character)
+    purrr::map_lgl(
+      rec$template %>% dplyr::select(dplyr::one_of(nominal)),
+      rlang::is_character
+    )
   if (any(is_str)) {
     selector <- rlang::expr(one_of(!!!nominal[is_str]))
     step_expr <- rlang::expr(step_string2factor(!!selector))
@@ -139,10 +143,12 @@ template_workflow <- function(prefix) {
 
 template_tune_with_grid <- function(prefix, colors = TRUE) {
   tune_expr <-
-    rlang::call2("tune_grid",
-                 sym(paste0(prefix, "_workflow")),
-                 resamples = expr(stop("add your rsample object")),
-                 grid = sym(paste0(prefix, "_grid")))
+    rlang::call2(
+      "tune_grid",
+      sym(paste0(prefix, "_workflow")),
+      resamples = expr(stop("add your rsample object")),
+      grid = sym(paste0(prefix, "_grid"))
+    )
   res <- assign_value(paste0(prefix, "_tune"), !!tune_expr)
   if (colors) {
     res <- sub(
@@ -163,8 +169,10 @@ template_tune_no_grid <- function(prefix, seed = sample.int(10^5, 1), colors = T
       grid = expr(stop("add number of candidate points"))
     )
 
-  res <- c(paste0("set.seed(", seed,")\n"),
-           assign_value(paste0(prefix, "_tune"), !!tune_expr))
+  res <- c(
+    paste0("set.seed(", seed, ")\n"),
+    assign_value(paste0(prefix, "_tune"), !!tune_expr)
+  )
 
   if (colors) {
     res <- sub(
@@ -186,9 +194,9 @@ template_tune_no_grid <- function(prefix, seed = sample.int(10^5, 1), colors = T
 # Take the call to the template function and turn it into a call to `recipe()`
 initial_recipe_call <- function(cl) {
   cl$tune <- NULL
-  cl$verbose <-  NULL
-  cl$colors <-  NULL
-  cl$prefix <-  NULL
+  cl$verbose <- NULL
+  cl$colors <- NULL
+  cl$prefix <- NULL
   rec_cl <- cl
   rec_cl[[1]] <- rlang::expr(recipe)
   rec_cl