-
Notifications
You must be signed in to change notification settings - Fork 21
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
Consideration of additional pre-processing helper functions #404
Comments
No, no strong view. It's slightly more maintenance but the small improvement in workflows may be worth it. It can be added as a test and its usefulness can be reevaluated later down the line. If possible, I would recommend to try and be consistent in your usage in examples & vignettes. Promoting two ways to do the same task can be confusing for new users and being clear on what is the "officially recommended" workflow can help. |
Thanks, good points.
Yes definitely. The only downside I see for this is if we exposed all arguments for the inner two functions that the wrapper would have quite a few. We might need to workshop the name a bit as well as its a bit vague maybe? |
@medewitt any chance you've got capacity to take this one? |
@seabbs happy to take this on if it can wait until early May...a bit swamped through April. |
Yeah that would be no problem - amazing! Good luck getting through the swamp! |
Is your feature request related to a problem? Please describe.
During the course of #402 we created a helper function for the test suite.
As many of these pre-processing steps are likely to be chained together in repeatable pipelines, there might be an opportunity to provide users with a consolidated helper function.
Describe the solution you'd like
A series of helper functions which chain the pre-processing steps for input data that are often the most repeated with sensible defaults.
Describe alternatives you've considered
Leaving the pre-processing steps discrete allows for easier debugging should an error occur and potentially less code burden to maintain.
However, users will likely create these helper functions on their own and providing some streamlined defaults could help with package adoption and ease in productionalising.
Additional context
N/A
The text was updated successfully, but these errors were encountered: