Vedha Viyash

@donyunardi could be because some of the packages are release versions. I used the dev version of all packages and did not get this error.

Here are some of my thoughts. ## 1. Transform mechanism I think right now the complete `teal_data` is being passed to the transform module, so even the datanames not in...

> What are you thinking about such API I think this is feature-rich, and provides more customizability. The thing that is not clear to me is that `teal_slices` is something...

These enhancements were observed by @pawelru when working on https://github.com/insightsengineering/teal.modules.clinical/pull/983

Issue related to warnings is raised in [shinytest2](https://github.com/rstudio/shinytest2/issues/378)

R version bumped in PR #1440

I don't think we should return `shiny.appobj` from `teal::init()` if we did this we would have to support other arguments to be passed into `init` like `enableBookmarking`. I misinterpreted the...

I like the idea. And, this would be the only time when we could do this breaking change without many users getting affected by it, as we release it for...

`teal_init` would be ridiculous! And I would not change it cause we also call it `rhino::init` ;) When you put it this way it does not feel very odd to...

@lcd2yyz What do you think about implementing [cicerone](https://cicerone.john-coene.com/) to create guided tours instead of documenting about this extensively? I see a risk of a teal user getting overwhelmed by all...