ShinyHierarchy: ShinyHierarchy

In mexindian/ShinyTester: Functions to Minimize Bonehead Moves While Working with 'shiny'

Description

Create a hierarchical network chart that shows the _ad hoc_ structure of your shiny Server.

Usage

ShinyHierarchy(directory = getwd(), ui = "ui.R", server = "server.R",
  offsetReactives = T, showInternalFunctions = F,
  showCommentedOutChunks = F, output = "network")

Arguments

directory	the directory or website containing the files for the Shiny App. Defaults to current working directory
ui	a character vector size 1 containing the name of the UI files. defaults to "ui.R"
server	a character vector size 1 containing the names of the SERVER file. defaults to "server.R"
offsetReactives	a boolean that specifies if the middle row (the reactives) should show up in one row or whether there should be a small offset. TRUE by default.
showInternalFunctions	a boolean that specifies whether to show the functions internal to each node. These are shown on mouse_over in the hierarchy chart. FALSE by default.
showCommentedOutChunks	a boolean that specifies whether to show the chunks that have been commented out. FALSE by default.
output	a character string that specifies what kind of plot should be outputted: either "network" or "sankey" are accepted.

Details

You can test with your own app, go to your shiny app, make that your working directory, and then type 'ShinyHierarchy()'

Value

It returns a very very nice network chart with BASICALLY three-ish ROWS of nodes. The first one is the UI Inputs, the middle row(s) are the reactives, and the last row are the outputs being visualized. The hesitation for the second row (the reactives) is because I have introduced a small offset to each node in the middle row in order to see reactive flows into each other (if they are all in the same row, you can't really see them). You can avoid this behavior by setting the parameter offsetReactives = F.

Examples

ShinyHierarchy(system.file("example", package = "ShinyTester"))

mexindian/ShinyTester documentation built on May 25, 2021, 2:08 p.m.