Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In General #158

Open
npaszty opened this issue Jun 9, 2022 · 0 comments
Open

In General #158

npaszty opened this issue Jun 9, 2022 · 0 comments
Labels

Comments

@npaszty
Copy link
Contributor

npaszty commented Jun 9, 2022

There are several cases across the package where variables are hard coded into the modules. would like to have this scrubbed so that there is more flexibility for example to use treatment variables other than ARM and ACTARM.

What this causes is potential disconnect between study analysis and visualizations in the app. when study analysis uses TRT01P and TRT01A treatment variables then there are cases where the values can differ for the same patient between let's say ACTARM and TRT01A.

users should be able to configure the trt_group input to include treatment variables other then ARM and ACTARM.

Current

trt_group = choices_selected(c("ARM", "ACTARM"), "ARM")

Users should be able to do

trt_group = choices_selected(c("TRT01P", "TRT01A"), "TRT01P"),

but then code like this will be troublesome. note spelling of facetting should be faceting

      validate(need(
        !facet_var %in% c("ACTARM", "ARM")[!c("ACTARM", "ARM") %in% trt_group],
        sprintf("You can not choose %s as facetting variable for treatment variable %s.", facet_var, trt_group)
      ))

would be very helpful to have hard coded references to variables across the teal.goshawk package to be removed.

@npaszty npaszty added enhancement New feature or request priority refactor labels Jun 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant