mirror of
https://github.com/rstudio/shiny.git
synced 2026-01-10 07:28:01 -05:00
dde266768c
These functions were temporarily ripped out of Shiny and moved to the htmltools package. We've discovered that it's safe to keep including them in shiny; as long as the functions in shiny and the functions in htmltools are identical, the user won't receive a conflict warning.
26 lines
819 B
R
26 lines
819 B
R
% Generated by roxygen2 (4.0.1): do not edit by hand
|
|
\name{markRenderFunction}
|
|
\alias{markRenderFunction}
|
|
\title{Mark a function as a render function}
|
|
\usage{
|
|
markRenderFunction(uiFunc, renderFunc)
|
|
}
|
|
\arguments{
|
|
\item{uiFunc}{A function that renders Shiny UI. Must take a single argument:
|
|
an output ID.}
|
|
|
|
\item{renderFunc}{A function that is suitable for assigning to a Shiny output
|
|
slot.}
|
|
}
|
|
\value{
|
|
The \code{renderFunc} function, with annotations.
|
|
}
|
|
\description{
|
|
Should be called by implementers of \code{renderXXX} functions in order to
|
|
mark their return values as Shiny render functions, and to provide a hint to
|
|
Shiny regarding what UI function is most commonly used with this type of
|
|
render function. This can be used in R Markdown documents to create complete
|
|
output widgets out of just the render function.
|
|
}
|
|
|