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
The current filtering behavior in dv.manager fits the needs of most of our modules, but some of them could benefit from more customized filtering behaviors. Those could be easily achieved by having dv.manager provide modules with some extra knowledge on the data it is provided and the state of dv.filter.
Would it be possible to extend this list with ...?
unfiltered_datasets: Non-reactive named list of datasets provided to dv.manager.
selected_dataset: Reactive list with these two elements:
name: character(1) identifying the selected dataset
filter_mask: logical(n) identifying the records of the selected dataset that pass the criteria selected in dv.filter.
The non-reactive nature of unfiltered_datasets could allow, among other things to perform checks or populate menus prior to reactive time.
The batching of the two selected_dataset elements inside a single reactive would ensure the atomicity of the information and avoid modules receiving desynchronized name+mask information.
This information is readily available in dv.manager so no significant extra processing would be required.
The text was updated successfully, but these errors were encountered:
The current filtering behavior in
dv.manager
fits the needs of most of our modules, but some of them could benefit from more customized filtering behaviors. Those could be easily achieved by havingdv.manager
provide modules with some extra knowledge on the data it is provided and the state ofdv.filter
.Would it be possible to extend this list with ...?
unfiltered_datasets
: Non-reactive named list of datasets provided todv.manager
.selected_dataset
: Reactive list with these two elements:name
:character(1)
identifying the selected datasetfilter_mask
:logical(n)
identifying the records of the selected dataset that pass the criteria selected indv.filter
.The non-reactive nature of
unfiltered_datasets
could allow, among other things to perform checks or populate menus prior to reactive time.The batching of the two
selected_dataset
elements inside a single reactive would ensure the atomicity of the information and avoid modules receiving desynchronizedname
+mask
information.This information is readily available in
dv.manager
so no significant extra processing would be required.The text was updated successfully, but these errors were encountered: