Skip to contents

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 module2app

module_ui,module_server

Module functions.

ui_args,server_args

Additional arguments passed to module_serverand module_ui. server_args can be shiny::reactive()s, if corresponding argument in module_server accepts it.

ui_wrapper

A function to wrap the resulting shiny::tagList() in. Must yield a full shiny UI, such as shiny::basicPage() or shiny::bootstrapPage(). For maximum reusability of a module, avoid depending on the wrapper and only return "vanilla" UI.

options

Named options that should be passed to the runApp call (these can be any of the following: "port", "launch.browser", "host", "quiet", "display.mode" and "test.mode"). You can also specify width and height parameters 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.

Functions

  • x_counter_button_app(): Test app

  • x_counter_button_ui(): Module UI

  • x_counter_button_server(): Module Server