slicer2UI(id)
slicer2(input, output, session, datatable, uiSequence, serverFunction,
uiFunction, ...)
Arguments
| id |
An id string that corresponds with the id used to call the module's UI function. |
| input |
shiny server input object |
| output |
shiny server output object |
| session |
shiny server session object |
| datatable |
A reactive data.table. |
| uiSequence |
A data.table with columns category, uiType,
and (optionally) possibleValues.
Both lists should contain elements of type character.
The category column should contain names of the categories
which will be subsequently fixed.
The uiType column should contain corresponding UI
which should be applied for each category choice.
The possibleValues column should contain a list of
the possible values for category.
If not supplied, possible values for each level of the list
will be determined based on the data.
Currently there are two possible UI types to perform: "tab" and "box",
which both make use of shinydashboard. |
| serverFunction |
A summary module server function.
This function should take, at minimum, the following arguments:
datatable and id.
Additional named arguments are passed via ....
Users have access to the full data.table if they need it
(e.g., to calculate histogram breaks) via .dtFull,
as well as a list of the currently selected category values
via .current.
Inside the function there should be a call to a shiny
module server function using the id.
See example section and compare with link[shiny]{callModule}). |
| uiFunction |
A summary module function UI taking one argument: id.
Note: the id value is generated internally.
Inside the function there should be a call to shiny module UI function.
See example section. |
| ... |
Additional arguments passed to serverFunction. |