You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have one single Shiny module that handles the generation of the summary plots for the dashboard.
Testing
No response
Documentation
No response
Dependencies
No response
Details and Comments
Currently, there are mod_monthly_count and mod_stat_numeric, but these do largely the same. So in order to make the code more DRY we could have a single mod_plots module with a server function that handles the different plot types. In the main app_server we would then have something like:
* Only check envvars when running in prod
* Update tests: module servers should fail on missing inputs
* Fix: get rid of warning/error at app startup when no concept is selected yet
Use `shiny::req()` to simplify checking for existence of reactive inputs
* Refactor: use single module for dashboard plots
* Refactor: update UI elements for plots
* Make plotting module generic for the type of plot
Fixes#30
* Move common module server tests to `test-mod_plots.R`
* Rename test files, they now only only contain business-logic tests
* Remove old modules
* Update doc
* Pass linter
Definition of Done / Acceptance Criteria
We have one single Shiny module that handles the generation of the summary plots for the dashboard.
Testing
No response
Documentation
No response
Dependencies
No response
Details and Comments
Currently, there are
mod_monthly_count
andmod_stat_numeric
, but these do largely the same. So in order to make the code more DRY we could have a singlemod_plots
module with a server function that handles the different plot types. In the mainapp_server
we would then have something like:The text was updated successfully, but these errors were encountered: