register tune_args() and tunable() methods unconditionally

[simonpcouch]

Closes #192. :)

[simonpcouch]

Seemed okay from my end, but worth double checking that this is indeed still the case with the changes in tidymodels/recipes#1087:

workflows/R/generics.R

Lines 14 to 16 in cce255e

	# This also has the side effect of loading recipes, ensuring that its
	# S3 methods for `required_pkgs()` are registered
	if (!is_installed("recipes")) {

[hfrick]

Why is required_pkgs() part of this PR? 🤔

re tune_args() and tunable(): When I moved them here, I originally also (re)exported the generic but @DavisVaughan suggested not to do that. IIRC, the reasoning was that you only really call those functions once you are in {tune} but not when you have only {workflows} loaded. #123 (comment)

I think this still holds so I'd remove the @export tag from the imported generics (not the methods, of course)

[DavisVaughan]

I would not re-export any of the generics

[hfrick]

Looks great!

As an additional comment, not part of this PR: there are tests for tune_args() and tunable() methods in extratests:

• https://github.com/tidymodels/extratests/blob/main/tests/testthat/test-tune_args.R
• https://github.com/tidymodels/extratests/blob/main/tests/testthat/test-tunable.R

do you think it's worth consolidating them with the tests here?

[simonpcouch]

Certainly worth looking into. :) Just opened up a separate issue, thanks!

[github-actions]

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.