What guidance should developers of Tidymodels extensions follow?

Machine Learning and Modeling
, , ,
1

I'm developing a {recipes} + {dials} extension called {tdarec}. I've referred often to the documentation on developer functions and to the organization of existing extensions. Still there are some questions i haven't found solid answers to. Is there (maybe only in development) a guidance document for extending Tidymodels?

In lieu of such, i do have one specific question: Under what circumstances should an extension include the Tidymodels package(s) it's extending in Depends versus Imports? I've been discussing this with my collaborator here.

Thank you!

2

Hey there!

You may find the dev checklists on the parsnip website helpful here.

As for Depends vs Imports: extension packages for specific tidymodels packages tend to list the core tidymodels package as a Depends, as yall have noted in the issue. While, in general, the tidy team advises folks to prefer Imports, it seems reasonable to list recipes and dials as Depends in this case.

3

Thank you!

Would a draft checklist for pre-processing and tuning functions be welcome? I wouldn't catch everything but i'd be glad to initialize it for future developers' benefit.