Error: 'filter' is not an exported object from 'namespace:duckplyr #632
-
So I was on
What has changed and how can I solve it? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Thanks, good question. The most important related change is that duckplyr no longer reexports all of dplyr's functions and methods. For writing a script, this should be of little relevance because duckplyr still depends on dplyr. See the "Loading required package" in the output: options(conflicts.policy = list(warn = FALSE))
library(duckplyr)
#> Loading required package: dplyr
#> ✔ Overwriting dplyr methods with duckplyr methods.
#> ℹ Turn off with `duckplyr::methods_restore()`. Created on 2025-03-02 with reprex v2.1.1 For packages and other more advanced setups, you now need to import #' @importFrom dplyr filter
NULL Do you think our documentation needs more work here? |
Beta Was this translation helpful? Give feedback.
Thanks, good question. The most important related change is that duckplyr no longer reexports all of dplyr's functions and methods. For writing a script, this should be of little relevance because duckplyr still depends on dplyr. See the "Loading required package" in the output:
Created on 2025-03-02 with reprex v2.1.1
For packages and other more advanced setups, you now need to import
filter()
from the dplyr namespace, perhaps using roxygen2:Do you think…