From 152bd5841cf2c44712cfdfa784bda1866810cdba Mon Sep 17 00:00:00 2001 From: trestletech Date: Wed, 19 Jun 2019 15:29:54 -0500 Subject: [PATCH] Accept whitespace-only RD changes. --- man/absolutePanel.Rd | 3 +-- man/brushedPoints.Rd | 6 ++---- man/diskCache.Rd | 3 +-- man/fixedPage.Rd | 3 +-- man/fluidPage.Rd | 3 +-- man/getQueryString.Rd | 3 +-- man/memoryCache.Rd | 3 +-- man/nearPoints.Rd | 3 +-- man/radioButtons.Rd | 3 +-- man/submitButton.Rd | 3 +-- man/validate.Rd | 3 +-- 11 files changed, 12 insertions(+), 24 deletions(-) diff --git a/man/absolutePanel.Rd b/man/absolutePanel.Rd index bb2c261fe..17966996b 100644 --- a/man/absolutePanel.Rd +++ b/man/absolutePanel.Rd @@ -77,6 +77,5 @@ such as \code{"100px"} (100 pixels) or \code{"25\%"}. For arcane HTML reasons, to have the panel fill the page or parent you should specify \code{0} for \code{top}, \code{left}, \code{right}, and \code{bottom} -rather than the more obvious \code{width = "100\%"} and \code{height = -"100\%"}. +rather than the more obvious \code{width = "100\%"} and \code{height = "100\%"}. } diff --git a/man/brushedPoints.Rd b/man/brushedPoints.Rd index 1760b47f9..940903b5f 100644 --- a/man/brushedPoints.Rd +++ b/man/brushedPoints.Rd @@ -43,16 +43,14 @@ The \code{xvar}, \code{yvar}, \code{panelvar1}, and \code{panelvar2} arguments specify which columns in the data correspond to the x variable, y variable, and panel variables of the plot. For example, if your plot is \code{plot(x=cars$speed, y=cars$dist)}, and your brush is named -\code{"cars_brush"}, then you would use \code{brushedPoints(cars, -input$cars_brush, "speed", "dist")}. +\code{"cars_brush"}, then you would use \code{brushedPoints(cars, input$cars_brush, "speed", "dist")}. For plots created with ggplot2, it should not be necessary to specify the column names; that information will already be contained in the brush, provided that variables are in the original data, and not computed. For example, with \code{ggplot(cars, aes(x=speed, y=dist)) + geom_point()}, you could use \code{brushedPoints(cars, input$cars_brush)}. If, however, you use -a computed column, like \code{ggplot(cars, aes(x=speed/2, y=dist)) + -geom_point()}, then it will not be able to automatically extract column names +a computed column, like \code{ggplot(cars, aes(x=speed/2, y=dist)) + geom_point()}, then it will not be able to automatically extract column names and filter on them. If you want to use this function to filter data, it is recommended that you not use computed columns; instead, modify the data first, and then make the plot with "raw" columns in the modified data. diff --git a/man/diskCache.Rd b/man/diskCache.Rd index ef9e6988a..fe4bba77e 100644 --- a/man/diskCache.Rd +++ b/man/diskCache.Rd @@ -73,8 +73,7 @@ function for \code{missing} that takes one argument, the key, and also use When the cache is created, you can supply a value for \code{missing}, which sets the default value to be returned for missing values. It can also be overridden when \code{get()} is called, by supplying a \code{missing} -argument. For example, if you use \code{cache$get("mykey", missing = - NULL)}, it will return \code{NULL} if the key is not in the cache. +argument. For example, if you use \code{cache$get("mykey", missing = NULL)}, it will return \code{NULL} if the key is not in the cache. If your cache is configured so that \code{get()} returns a sentinel value to represent a cache miss, then \code{set} will also not allow you to store diff --git a/man/fixedPage.Rd b/man/fixedPage.Rd index 100ab6573..cde6f247d 100644 --- a/man/fixedPage.Rd +++ b/man/fixedPage.Rd @@ -41,8 +41,7 @@ layout functions like \code{sidebarLayout}, rather, all layout must be done with \code{fixedRow} and \code{column}. } \note{ -See the \href{http://shiny.rstudio.com/articles/layout-guide.html}{ -Shiny Application Layout Guide} for additional details on laying out fixed +See the \href{http://shiny.rstudio.com/articles/layout-guide.html}{ Shiny Application Layout Guide} for additional details on laying out fixed pages. } \examples{ diff --git a/man/fluidPage.Rd b/man/fluidPage.Rd index f9918ca80..305839c12 100644 --- a/man/fluidPage.Rd +++ b/man/fluidPage.Rd @@ -40,8 +40,7 @@ alternative to low-level row and column functions you can also use higher-level layout functions like \code{\link{sidebarLayout}}. } \note{ -See the \href{http://shiny.rstudio.com/articles/layout-guide.html}{ -Shiny-Application-Layout-Guide} for additional details on laying out fluid +See the \href{http://shiny.rstudio.com/articles/layout-guide.html}{ Shiny-Application-Layout-Guide} for additional details on laying out fluid pages. } \examples{ diff --git a/man/getQueryString.Rd b/man/getQueryString.Rd index eb2b97e6a..64a366416 100644 --- a/man/getQueryString.Rd +++ b/man/getQueryString.Rd @@ -14,8 +14,7 @@ getUrlHash(session = getDefaultReactiveDomain()) } \value{ For \code{getQueryString}, a named list. For example, the query -string \code{?param1=value1¶m2=value2} becomes \code{list(param1 = - value1, param2 = value2)}. For \code{getUrlHash}, a character vector with +string \code{?param1=value1¶m2=value2} becomes \code{list(param1 = value1, param2 = value2)}. For \code{getUrlHash}, a character vector with the hash (including the leading \code{#} symbol). } \description{ diff --git a/man/memoryCache.Rd b/man/memoryCache.Rd index be632e69f..7e34b5f71 100644 --- a/man/memoryCache.Rd +++ b/man/memoryCache.Rd @@ -72,8 +72,7 @@ function for \code{missing} that takes one argument, the key, and also use When the cache is created, you can supply a value for \code{missing}, which sets the default value to be returned for missing values. It can also be overridden when \code{get()} is called, by supplying a \code{missing} -argument. For example, if you use \code{cache$get("mykey", missing = - NULL)}, it will return \code{NULL} if the key is not in the cache. +argument. For example, if you use \code{cache$get("mykey", missing = NULL)}, it will return \code{NULL} if the key is not in the cache. If your cache is configured so that \code{get()} returns a sentinel value to represent a cache miss, then \code{set} will also not allow you to store diff --git a/man/nearPoints.Rd b/man/nearPoints.Rd index 4daeb92c4..87383b178 100644 --- a/man/nearPoints.Rd +++ b/man/nearPoints.Rd @@ -68,8 +68,7 @@ The \code{xvar}, \code{yvar}, \code{panelvar1}, and \code{panelvar2} arguments specify which columns in the data correspond to the x variable, y variable, and panel variables of the plot. For example, if your plot is \code{plot(x=cars$speed, y=cars$dist)}, and your click variable is named -\code{"cars_click"}, then you would use \code{nearPoints(cars, -input$cars_brush, "speed", "dist")}. +\code{"cars_click"}, then you would use \code{nearPoints(cars, input$cars_brush, "speed", "dist")}. } \examples{ \dontrun{ diff --git a/man/radioButtons.Rd b/man/radioButtons.Rd index d7ef6ad54..56482ebe4 100644 --- a/man/radioButtons.Rd +++ b/man/radioButtons.Rd @@ -45,8 +45,7 @@ Create a set of radio buttons used to select an item from a list. } \details{ If you need to represent a "None selected" state, it's possible to default -the radio buttons to have no options selected by using \code{selected = -character(0)}. However, this is not recommended, as it gives the user no way +the radio buttons to have no options selected by using \code{selected = character(0)}. However, this is not recommended, as it gives the user no way to return to that state once they've made a selection. Instead, consider having the first of your choices be \code{c("None selected" = "")}. } diff --git a/man/submitButton.Rd b/man/submitButton.Rd index 69385f972..7f04211ba 100644 --- a/man/submitButton.Rd +++ b/man/submitButton.Rd @@ -28,8 +28,7 @@ the more versatile \code{\link{actionButton}} (see details below). Submit buttons are unusual Shiny inputs, and we recommend using \code{\link{actionButton}} instead of \code{submitButton} when you want to delay a reaction. -See \href{http://shiny.rstudio.com/articles/action-buttons.html}{this -article} for more information (including a demo of how to "translate" +See \href{http://shiny.rstudio.com/articles/action-buttons.html}{this article} for more information (including a demo of how to "translate" code using a \code{submitButton} to code using an \code{actionButton}). In essence, the presence of a submit button stops all inputs from diff --git a/man/validate.Rd b/man/validate.Rd index 8500f52b9..04a351c80 100644 --- a/man/validate.Rd +++ b/man/validate.Rd @@ -60,8 +60,7 @@ the following: If any of these values happen to be valid, you can explicitly turn them to logical values. For example, if you allow \code{NA} but not \code{NULL}, you -can use the condition \code{!is.null(input$foo)}, because \code{!is.null(NA) -== TRUE}. +can use the condition \code{!is.null(input$foo)}, because \code{!is.null(NA) == TRUE}. If you need validation logic that differs significantly from \code{need}, you can create other validation test functions. A passing test should return