teal icon indicating copy to clipboard operation
teal copied to clipboard

Exploratory Web Apps for Analyzing Clinical Trial Data

Results 136 teal issues
Sort by recently updated
recently updated
newest added

In the preprocessing app developer can add `library(pkg)` calls in the `eval_code/within` call. Thanks to this code in `qenv/teal_data` will contain `library` calls, so will be more reproducible. ``` data...

core

Remove `get_rcode_libraries` definition and its usage.

core

# Pull Request Part of https://github.com/insightsengineering/coredev-tasks/issues/503 đŸŽ¯ ℹī¸ Targets `@main` and (`898_save_app_state3` silently) - synced with latest e2e developments and bookmarking feature 👀 changed files of this PR are under:...

blocked

### Feature description Currently the Reporter in "Variable Browser" module includes only a plot in a report. Would be nice to include a statistic table below the plot in the...

enhancement
core

After https://github.com/insightsengineering/teal/pull/1051 on pre-release branch we are using MultiAssayExperiment only in: - tests of deprecated functionality (`tdata()`) - vignette "Including Data in teal Applications" (please note that it's not used...

core

### What is your question? I am trying to restrict user access to different teal modules in an app and I need to identify the current session user and control...

question
core

### What happened? Some of the packages are displayed twice in the SRC. Tested devel deploy of exploratory app - Table Choices module - https://genentech.shinyapps.io/nest_exploratory_dev/ ### sessionInfo() ```R R version...

bug
core

> This introduces a coupling to the ids defined in `teal.reporter`. If we ever change it for some reason - `teal` would have to be re-released. The same goes with...

core

Nowadays I think `rvest` is just a wrapper around `xml2`. Maybe we can work directly with `xml2`? See `namespace:xml2` ```r > rvest::read_html function (x, encoding = "", ..., options =...

core

### Feature description ### Problem `{shinytest2}` e2e tests are currently created around `AppDriver$set_input` that will make the necessary changes via `javascript: Shiny.setInput` function (within `{chromote}` session). Current approach successfully tests...

enhancement
core