What does change is code like that:
some_vector <- list(some_values = c("value_1", "value_2"))
df %>%
dplyr::filter(x %in% some_vector$some_values)
If your df is a remote database connection, then dbplyr will assume that some_vector is a column in your remote dataset and will try to look for some_values in it. To avoid that, you'll want to do something like what is suggested in the error message:
some_vector <- list(some_values = c("value_1", "value_2"))
df %>%
dplyr::filter(x %in% !!some_vector$some_values)
# or
some_vector <- list(some_values = c("value_1", "value_2"))
df %>%
dplyr::filter(x %in% local(some_vector$some_values))
The reason this is happening is because most modern DB's have some support for json and now some_vector$some_values can be used to extract some_values element from some_vector in your DB. Therefore, you need to explicitly tell dbplyr where to look for some_vector$some_values