-
Notifications
You must be signed in to change notification settings - Fork 21
Export recompose()
#231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export recompose()
#231
Conversation
Since recipes allows for this. We don't want this in the hardhat blueprints though, as we'd prefer to nudge people towards tibbles, which hardhat tries hard to generate internally.
| #' @description | ||
| #' `recompose()` takes a data frame and converts it into one of: | ||
| #' - A tibble | ||
| #' - A data frame |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added support for "data.frame" specifically for recipes, but hardhat won't use it
| #' The output type is determined from the `composition`. | ||
| #' | ||
| #' @export | ||
| #' @keywords internal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Internal as I don't really want people using this
EmilHvitfeldt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checked in recipes. Looks good!
This is great, removing this duplicated logic is going to be nice
|
This pull request 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. |
Closes #220
It looks like
recompose()is really what we want to use in recipes