insightsengineering / insightsengineering/teal.modules.general
Support interchangeably filter_spec and select_spec for all Inputs
- Dominant language
- R
- Stars
- 16
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
**It might be more research one.**
**The same task should be done for tmc. After solution is designed.**
We are developing our apps with certain type of Input. Nevertheless users might want to change them.
We should start we each module example app and make sure that each input could be changed between filter_spec/select_spec.
One problem might be with `extact_input` function which is used in a few modules (mostly in tmc). This function expecting static logical value specifying if the input is filter_spec or select_spec.
@pawelru suggested to return all needed ids with `data_merge_module`.
On the ui side we might think of returning the id by `data_extarc_input` (then they have to be pre-defined before usage `var <- data_extact_input...` and then var$id (to get id) and in ui directly `var`.
Contributor guide
Assessment
This issue has not been assessed yet.