-
Notifications
You must be signed in to change notification settings - Fork 3
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
Edits to grouping of validation errors #118
Comments
Where can I test the dev code? Also, do we have a sample file that triggers as many errors as possible? I'd like to review the grouping as I hadn't been notified on OpenDataServices/cove#1168. For instance, the "Format" group should probably be renamed "Type and Format" because "not a string" (type) is not the same type of error as "not a date" (format). The description text would likely have to be similarly updated. |
@jpmckinney sorry no-one got back to you on this at the time! See my response in OpenDataServices/cove#1180 regarding test data. Could you pull your comments from testing into a list of changes that you'd like to see and we can get it into the pipeline to get worked through? |
Some quick feedback from submitting: http://standard.open-contracting.org/review/?source_url=https://raw.githubusercontent.com/OpenDataServices/cove/master/cove_ocds/fixtures/badfile_all_validation_errors.json
|
Remaining issues are in this comment: #118 (comment), one of which is repeated in #120 |
See OpenDataServices/cove#1117 for how we did this for 360Giving.
Right now, all of the validation errors are presented in one table. Grouping these by type (eg missing-but-required, format errors, 'other') helps people understand what kind of things they need to do in order to make their data use the standard.
The task here is to:
The text was updated successfully, but these errors were encountered: