Tyler Littlefield

Awesome, thank you for the thorough response. We have gone with the nested table route, specifically something based on this [example](https://glin.github.io/reactable/articles/examples.html#conditional-row-details). This has been such a fun package to play...

Just wanted to say that this would be a great addition. If could set `filterable = TRUE` then `filterType = "dropdown"` it would simplify some of the apps I have...

@shahreyar-abeer To clarify, I use `selectInput` *outside* of the `reactable`, unlike the slider shown in @timelyportfolio‘s example (which is what I think you’re looking for).

Also running into this, has anyone came up with a workaround? If you remove the `nowrap` css it will wrap but it brings with it additional display issues.

Exactly what I needed, thanks!

I am struggling with this as well with ~20,000+ choices. I am thinking of using `updateSelectizeInput` based on advice from [Joe Cheng](https://community.rstudio.com/t/select-box-with-millions-of-choices/18241/6): ``` library(shiny) library(dplyr) baby_names % distinct(name) %>% .[["name"]]...

@lalitsc12 You should take a look at `shiny::selectizeInput`, it allows for server side processing.

@lalitsc12 That's correct, you can choose to render only 100 values but then search to render more values. It drastically improves performance.

~~Note that this doesn't work on footers however:~~ Just kidding, found this issue for a solution: https://github.com/glin/reactable/issues/78 ```r library(crosstalk) cars

> However, plumber docker files need to be able to fix to a specific R version. So until rocker/r-ver updates to allow for multiple architecture, I guess we are stuck....