We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Imports
Suggests
Currently, paletteer imports a number of palette packages only for a single function (mostly here: https://github.com/EmilHvitfeldt/paletteer/blob/37567c57aae4ba4368ad964b457db8148b808ff5/R/paletteer_c_wrappers.R), and I was wondering if it would be better to use them conditionally and move them to Suggests in DESCRIPTION instead of directly importing them.
paletteer
DESCRIPTION
This would also slightly reduce dependency load for packages like ggstatsplot that rely on paletteer.
ggstatsplot
For example-
#' @rdname paleteer-c-wrapper paletteer_c_scico <- function(name, n) { if (!requireNamespace("scico", quietly = TRUE)) { stop("Package 'scico' needed. Please install it by running `install.packages('scico')`.") } scico::scico(n = n, palette = name) }
What do you think?
The text was updated successfully, but these errors were encountered:
I like the idea! I'll try to whip it into the next update
Sorry, something went wrong.
35d2a79
No branches or pull requests
Currently,
paletteer
imports a number of palette packages only for a single function (mostly here: https://github.com/EmilHvitfeldt/paletteer/blob/37567c57aae4ba4368ad964b457db8148b808ff5/R/paletteer_c_wrappers.R), and I was wondering if it would be better to use them conditionally and move them toSuggests
inDESCRIPTION
instead of directly importing them.This would also slightly reduce dependency load for packages like
ggstatsplot
that rely onpaletteer
.For example-
What do you think?
The text was updated successfully, but these errors were encountered: