documentation changes for @NAMEs param - move to qenv-consrtuctor

Author: m7pr

R/qenv-constructor.R

@@ -33,6 +33,9 @@ qenv <- function() {
 #'  (`character(1)` or `language`) code to evaluate. Accepts and stores comments also.
 #' @param env `r badge("deprecated")` (`environment`)
 #'  Environment being a result of the `code` evaluation.
+#' @param names (`character`) for `x[names]`, names of objects included in `qenv` to subset. Names not present in `qenv`
+#' are skipped. For `get_code` `r lifecycle::badge("experimental")` vector of object names to return the code for.
+#' For more details see the "Extracting dataset-specific code" section.
 #'
 #' @examples
 #' # create qenv with data and code (deprecated)

R/qenv-extract.R

@@ -2,7 +2,6 @@
 #' @section Subsetting:
 #' `x[names]` subsets objects in `qenv` environment and limit the code to the necessary needed to build limited objects.
 #'
-#' @param names (`character`) names of objects included in `qenv` to subset
 #' @param x (`qenv`)
 #'
 #' @examples

R/qenv-get_code.R

@@ -5,13 +5,11 @@
 #'
 #' @param object (`qenv`)
 #' @param deparse (`logical(1)`) flag specifying whether to return code as `character` or `expression`.
-#' @param names `r lifecycle::badge("experimental")` (`character`) vector of object names to return the code for.
-#' For more details see the "Extracting dataset-specific code" section.
 #' @param ... see `Details`
 #'
 #'
 #' @section Extracting dataset-specific code:
-#' When `names` is specified, the code returned will be limited  to the lines needed to _create_
+#' When `names` for `get_code` is specified, the code returned will be limited  to the lines needed to _create_
 #' the requested objects. The code stored in the `@code` slot is analyzed statically to determine
 #' which lines the objects of interest depend upon. The analysis works well when objects are created
 #' with standard infix assignment operators (see `?assignOps`) but it can fail in some situations.