298 reset button

[chlebowa]

Relates to this issue.

Adds module for management of snapshots of application state.
A snapshot contains in formation on all filter states currently existing within the app, as well as their application to particular modules.
A snapshot can be added at any time by the user.
A snapshot can be restored at any time by the user.
A snapshot can be saved to file.
The initial state of the application is the first snapshot (not displayed in the list).

In addition, teal_slices handles global-module-specific specification differently. The deciding argument is module_specific. mapping$global_filters will decide which - if any - filters are active on start-up in global mode.

[chlebowa]

TESTING

Set teal and teal.slice to 298_reset_button@filter_panel_refactor@main
Use the following app.

options(teal.log_level = "WARN", teal.show_js_log = TRUE)
# options("teal.bs_theme" = bslib::bs_theme(version = 5))
# options(shiny.trace = TRUE)
# todo: change groupCheckbox to include locked (not able to interact with)
#       change groupCheckbox to have some colors (instead of grey)
# todo: available filter should present information about selected values (for example tooltip)

library(shiny)
library(scda)
library(scda.2022)
library(teal.data)
library(teal.transform)
library(teal.modules.general)
pkgload::load_all("../teal.slice")
pkgload::load_all("../teal")

funny_module <- function (label = "Filter states", datanames = "all") {
  checkmate::assert_string(label)
  module(
    label = label,
    filters = datanames,
    ui = function(id, ...) {
      ns <- NS(id)
      div(
        h2("The following filter calls are generated:"),
        verbatimTextOutput(ns("filter_states")),
        verbatimTextOutput(ns("filter_calls")),
        actionButton(ns("reset"), "reset_to_default")
      )
    },
    server = function(input, output, session, data, filter_panel_api) {
      checkmate::assert_class(data, "tdata")
      observeEvent(input$reset, set_filter_state(filter_panel_api, default_filters))
      output$filter_states <-  renderPrint({
        logger::log_trace("rendering text1")
        filter_panel_api %>% get_filter_state()
      })
      output$filter_calls <- renderText({
        logger::log_trace("rendering text2")
        attr(data, "code")()
      })
    }
  )
}

default_filters <- teal::teal_slices(
  teal_slice("iris", "Sepal.Length"),
  teal_slice("iris", "Sepal.Width"),
  teal_slice("iris", "Species"),
  teal_slice("mtcars", "mpg"),
  exclude_varnames = list(
    iris = c("Petal.Length"),
    mtcars = c("qsec", "drat")
  ),
  mapping = list(
    funny = c("iris Sepal.Length"),
    funny2 = c("iris Sepal.Width"),
    global_filters = "mtcars mpg"
  )
  # module_specific = FALSE
)
app <- init(
  data = teal_data(
    dataset("iris", iris),
    dataset("mtcars", mtcars)
  ),
  modules = modules(
    tm_data_table(
      "table",
      variables_selected = list(),
      dt_args = list()
    ),
    modules(
      label = "tab1",
      funny_module("funny", datanames = NULL),
      funny_module("funny2", datanames = "iris")
    )
  ),
  filter = default_filters
)

runApp(app, launch.browser = TRUE)

[gogonzo]

I consider technicals on the teal side robust.

[m7pr]

I love the elegancy of the graph/workflow

[chlebowa]

Great chart indeed @gogonzo and you beat me to it 🙂

I don't quite like the click either but since we can't think of anything better at the moment, let's put a pin in it, maybe we will come up with something later. Unless @lcd2yyz withdraws the requirement.

[gogonzo]

WOWs

[m7pr]

🔥

…

On Fri, Jul 21, 2023 at 10:25 AM Aleksander Chlebowski < ***@***.***> wrote: Merged #859 <#859> into main. — Reply to this email directly, view it on GitHub <#859 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A74AIENN2KSDJLNGLTEMT3DXRI4JFANCNFSM6AAAAAAZ3ONEYU> . You are receiving this because your review was requested.Message ID: ***@***.***>