elephantupthewrongtree

Using `TRUE` in `case_when` causes error if output vector length does not equal group size .N

1

_Originally posted by @KesterJ in https://github.com/tidyverse/dtplyr/issues/300#issuecomment-1036179822_ I've encountered a version of this issue that doesn't involve `&&`, and where `group_by()` is called after `lazy_dt()`. Reprex below: ``` r library(dplyr, warn.conflicts...

Splice data.frame inputs to `mutate`, `summarise`, and `transmute`

2

``` r library(dplyr, warn.conflicts = FALSE) library(dtplyr) df % mutate(data.frame(y = 2, z = 3)) #> # A tibble: 1 × 3 #> x y z #> #> 1 1...

feature request: Turn keyword highlighting off

1

I'd like keyword highlighting, but the dark blue is hard to read with a dark grey background. Would be nice if the option allowed specifying a color, but failing that...

`vec_unique` produces named output

11

I think it would be helpful to document that `vec_unique` produces named output if the arguments are named. The `help(vec_unique)` page says ays that `vec_unique` is "Equivalent to `unique()`" and...

data frame splicing in `j`

2

closes #454 This appears to work but I'm not sure how I feel about adding it. I'm not sure if there's a better option for `j` when there's more than...

e.g. 

`from_polars`?

3

I feel like I'm missing something, I see `from_pandas`, but surely there's a way to start from a polars dataframe too right?