Closed rsh52 closed 1 year ago
@skadauke @ezraporter In addition to the oneshot
call, there are 4 other REDCapR API calls involving the verbose
argument (metadata, arm, and instrument reads). Should suppress_redcapr_messages
extend to all API calls, or just oneshot
(keeping in mind how oneshot
may eventually be amended with #103/large databases). Is it more helpful to give users the option to see all results, or is this more confusing information than informative?
Expected Behavior
Supplying
suppress_redcapr_messages = FALSE
should allow for REDCapR messages to come through (instead of the default ofTRUE
).Current Behavior
Messages are always suppressed regardless of argument spec.
Proposed Solution
In the
REDCapR::redcap_read_oneshot
call, we currently haveverbose = FALSE
where instead it should beverbose = supress_redcapr_messages
.Checklist
Before submitting this issue, please check and verify below that the submission meets the below criteria: