|
1 | | -#' @title unListDS a serverside assign function called by ds.unList |
2 | | -#' @description this function is based on the native R function {unlist} |
| 1 | +#' |
| 2 | +#' @title \code{unListDS} a serverside assign function called by \code{ds.unList} |
| 3 | +#' @description this function is based on the native R function \code{unlist} |
3 | 4 | #' which coerces an object of list class back to the class it was when |
4 | 5 | #' it was coerced into a list |
5 | | -#' @details See details of the native R function {unlist}. |
| 6 | +#' @details See details of the native R function \code{unlist}. |
6 | 7 | #' This function represents a substantive restructuring of an earlier version |
7 | 8 | #' created by Amadou Gaye. For further details of its working please |
8 | | -#' see 'details' in the help for {ds.unList}. |
| 9 | +#' see 'details' in the help for \code{ds.unList}. |
9 | 10 | #' @param x.name the name of the input object to be unlisted. |
10 | 11 | #' It must be specified in inverted commas e.g. x.name="input.object.name". Fully |
11 | | -#' specified by the <x.name> argument of {ds.unList} |
12 | | -#' @return the object specified by the <newobj> argument of the |
13 | | -#' {ds.unList} function (or by default <x.name>.unlist |
14 | | -#' if the <newobj> argument is NULL). This is written to the serverside. |
15 | | -#' As well as writing the output object as <newobj> |
| 12 | +#' specified by the \code{x.name} argument of \code{ds.unList} |
| 13 | +#' @return the object specified by the \code{newobj} argument of the |
| 14 | +#' \code{ds.unList} function (or by default "unlist.newobj" |
| 15 | +#' if the \code{newobj} argument is NULL). This is written to the serverside. |
| 16 | +#' As well as writing the output object as \code{newobj} |
16 | 17 | #' on the serverside, two validity messages are returned |
17 | | -#' indicating whether <newobj> has been created in each data source and if so whether |
| 18 | +#' indicating whether \code{newobj} has been created in each data source and if so whether |
18 | 19 | #' it is in a valid form. If its form is not valid in at least one study - e.g. because |
19 | 20 | #' a disclosure trap was tripped and creation of the full output object was blocked - |
20 | | -#' {ds.seq()} also returns any studysideMessages that can explain the error in creating |
| 21 | +#' \code{ds.seq} also returns any studysideMessages that can explain the error in creating |
21 | 22 | #' the full output object. As well as appearing on the screen at run time,if you wish to |
22 | | -#' see the relevant studysideMessages at a later date you can use the {ds.message} |
| 23 | +#' see the relevant studysideMessages at a later date you can use the \code{ds.message} |
23 | 24 | #' function. If you type ds.message("<newobj>") it will print out the relevant |
24 | | -#' studysideMessage from any datasource in which there was an error in creating <newobj> |
25 | | -#' and a studysideMessage was saved. Because the outcome object from ds.unList is |
| 25 | +#' studysideMessage from any datasource in which there was an error in creating \code{newobj} |
| 26 | +#' and a studysideMessage was saved. Because the outcome object from \code{ds.unList} is |
26 | 27 | #' typically a list object with no names, if there are no errors in creating it |
27 | 28 | #' the message returned from ds.message("<newobj>") in each study will read |
28 | 29 | #' "Outcome object is a list without names. So a studysideMessage may be hidden. |
|
31 | 32 | #' the nature of the output from a call to ds.unList - e.g. ds.class, ds.length etc |
32 | 33 | #' @author Amadou Gaye (2016), Paul Burton (19/09/2019) for DataSHIELD Development Team |
33 | 34 | #' @export |
| 35 | +#' |
34 | 36 | unListDS <- function(x.name) { |
35 | 37 |
|
36 | 38 | if (is.character(x.name)) { |
|
0 commit comments