-
Notifications
You must be signed in to change notification settings - Fork 12
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
Suggested export options #119
Suggested export options #119
Conversation
Codecov Report
@@ Coverage Diff @@
## master #119 +/- ##
==========================================
+ Coverage 95.09% 95.22% +0.12%
==========================================
Files 24 25 +1
Lines 1142 1173 +31
==========================================
+ Hits 1086 1117 +31
Misses 56 56
Continue to review full report at Codecov.
|
Adding |
The first part (tracking the format) we certainly do... this gets the file extension which is saved in export_options as secuTrialR/R/read_export_options.R Line 143 in 385e5dc
Seems like a reasonable idea on the whole though |
@aghaynes so any changes(?), or can I go ahead and adjust the tests accordingly so we don't have 24 warnings? |
For me the addition of the warnings to read_secuTrial() would be fine. I'd also be OK with converting the warning to a message, if you prefer. |
Its ok with me |
@PatrickRWright should I merge now, or do you want to add something? |
I will go over the tests and remove the warnings if possible. Edit: Actually, I will change the warnings to messages as suggested by @markomi Also, how about having "English" as suggested language? Edit: I will do this. |
I'm done. |
Thanks @PatrickRWright! This will save us a lot of troubleshooting time. I'm merging. |
Pretty straight forward function to help people troubleshoot why "things" may not be working or train people what type of exports to request.
I would like to add the function call after
read_secuTrial_raw()
inread_secuTrial()
to warn people if they use the wrapper. What do you think @aghaynes @markomi ?Also I realized that we do not seem to be tracking the export format currently since we assume its always either "CSV format" or "CSV format for MS Excel". I think we should track this export option and catch it if e.g. SAS, CDISC, SPSS is specified. I have added this to the PR too.
closes #17