-
Notifications
You must be signed in to change notification settings - Fork 26
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
Better warning messages #14
Comments
Looking through the code, some places use suppressWarnings and maybe we could open those up and have better descriptive messages for those failures.
This is difficult. A user would want a warning message if the column was defined on the form and required, but no warnings otherwise. Exposing this could create more issues than it solves. |
I can recreate the unpaste warnings like this:
|
Context.... These
I would guess the original intent of |
Well we have some users who can test versus large databases, so I might do a test run against those. |
Theory: the field generating the error appears to be a "time" field. Are there any values that don't follow a strict
|
The underlying issue is they allowed text entry for a time field, later changed it to time and there's borked data in their REDCap. However, there are hundreds of fields and they just need to know which one. The jist of this request is better warning messages. |
I'm picking this one up. I know what to do. |
A user has reported the following warning messages and they would like to know the field names that are causing them.
We need test cases added that create these warnings on export. Then capture the warnings somehow and modify with the field name causing them.
The text was updated successfully, but these errors were encountered: