Skip to content

Commit

Permalink
chore: use base table instead of DT
Browse files Browse the repository at this point in the history
  • Loading branch information
vedhav committed Feb 3, 2025
1 parent bdaa160 commit e76b097
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 7 deletions.
1 change: 0 additions & 1 deletion DESCRIPTION
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,6 @@ Imports:
teal.widgets (>= 0.4.3),
utils
Suggests:
DT (>= 0.3.0),
knitr (>= 1.42),
MultiAssayExperiment,
rmarkdown (>= 2.23),
Expand Down
7 changes: 1 addition & 6 deletions vignettes/teal-slice.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -53,17 +53,12 @@ It also contains `shiny` modules (both UI and server functions) that make up the

In a `teal` application the `FilteredData` object (`datasets`) is created automatically by `teal`'s `init` function and filter panel components are automatically placed on the right-hand side of the page.

Note that this example uses `shiny::dataTableOutput` and `shiny::renderDataTable`.
This can lead to issues with Bootstrap, especially version 4.
We recommend using `DT::dataTableOutput` and `DT::renderDataTable` if possible. See the `shiny` and `DT` documentation for more information.

To facilitate communication with `FilteredData`, we provide the filter panel API.
The example below uses the `set_filter_state` function to set state and the state is specified with `teal_slices` and `teal_slice` functions.
For details please see the *Filter panel for developers* vignette.

```{r warning=FALSE, message=FALSE, eval=requireNamespace("DT", quietly = TRUE)}
```{r warning=FALSE, message=FALSE}
library(shiny)
library(DT)
library(teal.slice)
# create a FilteredData object
Expand Down

0 comments on commit e76b097

Please sign in to comment.