Skip to content
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

Data first functions #25

Closed
DavisVaughan opened this issue Feb 15, 2019 · 3 comments
Closed

Data first functions #25

DavisVaughan opened this issue Feb 15, 2019 · 3 comments

Comments

@DavisVaughan
Copy link
Member

scream(new_data, preprocessor, outcome) not scream(preprocessor, new_data, outcome)

@DavisVaughan
Copy link
Member Author

Actually don't do this. To be consistent everywhere we'd have to make forge() do the same thing, but it is S3 on the preprocessor argument. This would mean we would need to do UseMethod("forge", "preprocessor") because it would then be the second arg. This wouldn't be the end of the world but it likely more confusing that it would need to be.

@DavisVaughan
Copy link
Member Author

DavisVaughan commented Feb 15, 2019

Hmm, maybe do this with scream() and shrink() because they return new_data back as the output, but don't do it with forge() because it returns a more complicated object back (not pipeable anyways).

Nah, better to be consistent throughout

@github-actions
Copy link

github-actions bot commented Jul 1, 2021

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.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant