teal
teal copied to clipboard
insightsengineering
Exploratory Web Apps for Analyzing Clinical Trial Data
After this PR to `teal.widgets`: https://github.com/insightsengineering/teal.widgets/pull/59 the code inside the mentioned files should not be needed for anything. Investigate if it is safe to remove and remove if it is.
Please check out the Adding support for Reporting to custom module vignette taking into account current recommendations (tmg and tmc) and new developments.
We need some guidelines how to add the css rules to custom and the nest teal modules. Now we still use inline rules which are not recommended.
The reporter **UI** should be added to the module UI only if needed. This will make the modules more suited when used independently, outside the NEST. Another thing is that...
We need to set a formal rules how to support and maintain a js code from the teal developers side. The JS code is a significant part of the shiny...
We can avoid the busy waiting until the Shiny app has started with `Sys.sleep`. Otherwise, tests may be unnecessarily long. Here is the code. The app is defined as follows....
This I consider the navbar:  CSS position property explained: https://www.w3schools.com/css/css_positioning.asp This would be a little bit more complicated than just slamming the property on this HTML element because it...
Fixes https://github.com/insightsengineering/coredev-tasks/issues/479
An app built with the following `data` and `modules` (no filters) takes over a minute to start*, up to a minute and a half with `module_specific = TRUE`. The data...
### Feature description Move entire `teal` to [bslib](https://rstudio.github.io/bslib/)
Metadata
Owner
Metadata
Exploratory Web Apps for Analyzing Clinical Trial Data