Implement default selections

[jcheng5]

Fixes #35.

[mabecker89]

Thanks for this. Will this functionality be available soon?

[jcheng5]

I can't repro with Leaflet:

library(crosstalk)
library(leaflet)

sd <- SharedData$new(quakes)
filt <- filter_select(
  id = "mag",
  label = "Select magnitude",
  sharedData = sd,
  group = ~as.integer(mag),
  multiple = FALSE,
  selected = 5
)

map <- leaflet(sd) %>% addMarkers()

bscols(widths = c(3,9), filt, map)

@cpsievert, maybe something for us to take a quick look at together next week.

[Nova-Scotia]

This issue is still happening for me, like @paulklemm, using ggplotly and downloading from devtools::install_github("rstudio/crosstalk", ref = "joe/feature/filter-select-default").

[gtdca98]

Fixes #35.

(I would LOVE some help implementing the same for filter_checkbox and filter_slider.)

For filter_checkbox you can add at the end of flexdashboard <script > $('input[name="SelYear"][value=2020]').attr("checked", true); </script> assumming that "SelYear" is the id
filter_checkbox(id="SelYear", label = "", sharedData = sd19, group = ~YEAR, inline = FALSE)

[CLAassistant]

All committers have signed the CLA.

[paulklemm]

It seems that the problem I reported only happens with plotly. See @cpsievert post here: #16 (comment)

[ashishjain1988]

Is this feature has been updated? There is no "selected" argument in the latest CRAN update.

[cpsievert]

Thinking about this more, it seems better for selected to be specified through SharedData (either through $new() or via $selection()?), not the input controls. The benefit being that we'd also have a way to specify default selections (not just filter)

[mattkerlogue]

Hi, can I ask what the status of this PR is? I've been relying in a couple of toy projects on installing the branch version that implements this change, I'd like to use it in some production code (in a non-Shiny rmarkdown project) but would prefer to use the "main" version of the package rather than a branched offshoot.

[roaldarbol]

Would love to see this merged, but as it seems here 6 years on that it likely won't get merged (although it does provide much requested functionality) - could this PR at least be rebased so it would be up-to-date with main ?