Package 'brochure'

a list of elements to inject in the brochureApp. IMPORTANT NOTE all elements which are not of class "brochure_*" will be injected as is in the page. In other word, if you use a function that return a string, the string will be added as is to the pages. The only elements that should be injected on top of page()s are HTML elements and/or tagList/tags that are invisible on screen (for example a ⁠<script></script>⁠).

A function that will be called before the app is actually run. This is only needed for shinyAppObj, since in the shinyAppDir case, a global.R file can be used for this purpose.

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.

Can be one of "url", "server", or "disable". The default value, NULL, will respect the setting from any previous calls to enableBookmarking(). See enableBookmarking() for more information on bookmarking your app.

The content to dislay when a 404 is sent

The base path of your app. This pattern will be removed from the url, so that it matches the href of your page(). For example, it you have an app at ⁠http://connect.thinkr.fr/brochure/⁠, and your page is names page1, use basepath = "brochure"

a list of functions that can manipulate the req object. These functions should take req as a parameters, and return the req object (potentially modified), or an object of class httpResponse. If any of the req_handlers return an httpResponse, this response will be sent to the browser immeditately, stopping any other code.

A list of functions that can manipulate the httpResponse object before it is send to the browser. Each function must take a res and req parameter.

A UI function wrapping the Brochure UI. Default is shiny::tagList.

Name of the folder to create the package in. This will also be used as the package name.

Package name to use. By default, golem uses basename(path). If path == '.' & package_name is not explicitly set, then basename(getwd()) will be used.

Arguments passed from create_golem(), unused in the default function.

The name of the module.

The path to the R script where the module will be written. Note that this path will not be set by the user but via add_module().

Should the module be exported? Default is FALSE.

Arguments to be passed to the module_template function.

The endpoint to serve the UI on

The UI definition of the app (for example, a call to fluidPage() with nested controls).

If bookmarking is enabled (see enableBookmarking), this must be a single argument function that returns the UI definition.

A function with three parameters: input, output, and session. The function is called once for each session ensuring that each app is independent.

a list of functions that can manipulate the req object. These functions should take req as a parameters, and return the req object (potentially modified), or an object of class httpResponse. If any of the req_handlers return an httpResponse, this response will be sent to the browser immeditately, stopping any other code.

A list of functions that can manipulate the httpResponse object before it is send to the browser. Each function must take a res and req parameter.

The cookie string to parse

The {shiny} session object.

redirect from

redirect to

redirectin http code (one of c(301:308, 310))

the destination of the redirection

shiny session object, default is shiny::getDefaultReactiveDomain()

An httpResponse object

A cookie-name can be any US-ASCII characters, except control characters, spaces, or tabs. It also must not contain a separator character like the following: ⁠( ) < > @ , ; : \ " / [ ] ? = { }⁠.

[ ]: R:%20

A cookie-value can optionally be wrapped in double quotes and include any US-ASCII characters excluding control characters, Whitespace, double quotes, comma, semicolon, and backslash.

The maximum lifetime of the cookie as an HTTP-date timestamp. Please enter an ISO 8601 datetime format.

Number of seconds until the cookie expires. A zero or negative number will expire the cookie immediately. If both Expires and Max-Age are set, Max-Age has precedence.

Host to which the cookie will be sent.

A path that must exist in the requested URL, or the browser won't send the Cookie header.

Cookie is only sent to the server when a request is made with the https: scheme (except on localhost), and therefore is more resistent to man-in-the-middle attacks.

Forbids JavaScript from accessing the cookie, for example, through the Document.cookie property.

Controls whether a cookie is sent with cross-origin requests, providing some protection against cross-site request forgery attacks (CSRF).