Fix documentation note about links on r-devel

R/init.R

@@ -11,7 +11,7 @@
 #' `teal` app that is composed of `teal` modules.
 #'
 #' @param data (`teal_data` or `teal_data_module`)
-#'   For constructing the data object, refer to [teal_data()] and [teal_data_module()].
+#'   For constructing the data object, refer to [teal.data::teal_data()] and [teal_data_module()].
 #'   If `datanames` are not set for the `teal_data` object, defaults from the `teal_data` environment will be used.
 #' @param modules (`list` or `teal_modules` or `teal_module`)
 #'   Nested list of `teal_modules` or `teal_module` objects or a single

R/module_init_data.R

@@ -1,6 +1,6 @@
 #' Data Module for teal
 #'
-#' This module manages the `data` argument for `srv_teal`. The `teal` framework uses [teal_data()],
+#' This module manages the `data` argument for `srv_teal`. The `teal` framework uses [teal.data::teal_data()],
 #' which can be provided in various ways:
 #' 1. Directly as a [teal.data::teal_data()] object. This will automatically convert it into a `reactive` `teal_data`.
 #' 2. As a `reactive` object that returns a [teal.data::teal_data()] object.

R/module_teal_data.R

@@ -3,17 +3,17 @@
 #' This is a low level module to handle `teal_data_module` execution and validation.
 #' [teal_transform_module()] inherits from [teal_data_module()] so it is handled by this module too.
 #' [srv_teal()] accepts various `data` objects and eventually they are all transformed to `reactive`
-#' [teal_data()] which is a standard data class in whole `teal` framework.
+#' [teal.data::teal_data()] which is a standard data class in whole `teal` framework.
 #'
 #' @section data validation:
 #'
 #' Executed [teal_data_module()] is validated and output is validated for consistency.
 #' Output `data` is invalid if:
 #' 1. [teal_data_module()] is invalid if server doesn't return `reactive`. **Immediately crashes an app!**
-#' 2. `reactive` throws a `shiny.error` - happens when module creating [teal_data()] fails.
-#' 3. `reactive` returns `qenv.error` - happens when [teal_data()] evaluates a failing code.
-#' 4. `reactive` object doesn't return [teal_data()].
-#' 5. [teal_data()] object lacks any `datanames` specified in the `modules` argument.
+#' 2. `reactive` throws a `shiny.error` - happens when module creating [teal.data::teal_data()] fails.
+#' 3. `reactive` returns `qenv.error` - happens when [teal.data::teal_data()] evaluates a failing code.
+#' 4. `reactive` object doesn't return [teal.data::teal_data()].
+#' 5. [teal.data::teal_data()] object lacks any `datanames` specified in the `modules` argument.
 #'
 #' `teal` (observers in `srv_teal`) always waits to render an app until `reactive` `teal_data` is
 #' returned. If error 2-4 occurs, relevant error message is displayed to the app user. Once the issue is

R/teal_reporter.R

@@ -1,6 +1,6 @@
 #' @title `TealReportCard`
 #' @description `r lifecycle::badge("experimental")`
-#' Child class of [`ReportCard`] that is used for `teal` specific applications.
+#' Child class of [`teal.reporter::ReportCard`] that is used for `teal` specific applications.
 #' In addition to the parent methods, it supports rendering `teal` specific elements such as
 #' the source code, the encodings panel content and the filter panel content as part of the
 #' meta data.