Example of a nested module.
Usage
x_counter_button_app(...)
x_counter_button_ui(id)
x_counter_button_server(id, set_to = 2L, deep = FALSE)Arguments
- ...
Arguments passed on to
module2appmodule_ui,module_serverModule functions.
ui_args,server_argsAdditional arguments passed to
module_serverandmodule_ui.server_argscan beshiny::reactive()s, if corresponding argument inmodule_serveraccepts it.ui_wrapperA function to wrap the resulting
shiny::tagList()in. Must yield a full shiny UI, such asshiny::basicPage()orshiny::bootstrapPage(). For maximum reusability of a module, avoid depending on the wrapper and only return "vanilla" UI.optionsNamed options that should be passed to the
runAppcall (these can be any of the following: "port", "launch.browser", "host", "quiet", "display.mode" and "test.mode"). You can also specifywidthandheightparameters which provide a hint to the embedding environment about the ideal height/width for the app.
- id
The id string to be namespaced (optional).
- set_to
Giving the value to set the counter to.
- deep
Whether or not to return the inner module's reactive values. Only useful for testing, does not make much sense in this context.