From b26fe19ebaf69980774dec912eb99d51dd72a7bd Mon Sep 17 00:00:00 2001 From: Dawid Kaledkowski Date: Fri, 20 Dec 2024 10:45:34 +0100 Subject: [PATCH] update print --- R/teal_data-show.R | 3 ++- vignettes/teal-data.Rmd | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/R/teal_data-show.R b/R/teal_data-show.R index fca8cf66e..4ce54d8b8 100644 --- a/R/teal_data-show.R +++ b/R/teal_data-show.R @@ -16,5 +16,6 @@ setMethod("show", signature = "teal_data", function(object) { } else { cat("\u2716", "unverified teal_data object\n") } - rlang::env_print(teal.code::get_env(object)) + methods::callNextMethod(object) + invisible(object) }) diff --git a/vignettes/teal-data.Rmd b/vignettes/teal-data.Rmd index 93685f183..174bb2633 100644 --- a/vignettes/teal-data.Rmd +++ b/vignettes/teal-data.Rmd @@ -19,7 +19,7 @@ A `teal_data` is meant to be used for reproducibility purposes. The class inheri - `teal_data` is a locked environment, and data modification is only possible through the `teal.code::eval_code()` and `within.qenv()` functions. - It stores metadata about the code used to create the data (see [reproducibility](#reproducibility)). - It supports slicing by `[`. -- Is immutable which means that each code evaluation does not modify the original `teal_data` environment directly. +- It is immutable which means that each code evaluation does not modify the original `teal_data` environment directly. - It maintains information about relationships between datasets (see [Join Keys](#relational-data-models)). ## Quick Start