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
A list of simple todos extracted from code comments:
When using update_source (case when keep_na is integer or TRUE) use restore method based on limited state.
How can we allow to run add_step method when multiple filters are passed? Should we allow it?
Provide an option to save cohort state eveytime an operation changing state is run (e.g. add_step, rm_step etc and save states as a queue storing history).
In repro code generation we use multiple append calls. Maybe writing e.g. flatten_list method would simplify it?
When running .post_filtering we reassing the whole data. Can we optimize it to modify only "touched" datasets?
Source$update_filter - can we add more robustness when wrong filter ids are passed?
Can we extract choices from stats? Related to #47. When large dataset having only choices without computing stats can be faster.
Add column type - filter type validation (probably as optional as it needs some operations).
get_range_frequencies and get_date_range_frequencies - verify correctness and speedup (e.g. group_by can work slow).
The text was updated successfully, but these errors were encountered:
A list of simple todos extracted from code comments:
update_source
(case when keep_na is integer or TRUE) use restore method based on limited state.get_range_frequencies
andget_date_range_frequencies
- verify correctness and speedup (e.g. group_by can work slow).The text was updated successfully, but these errors were encountered: