-
Notifications
You must be signed in to change notification settings - Fork 2
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
Improve validation error messages (including oneOf) #16
Comments
This might be a dupe of a ticket in the BODS CRM? |
There's definitely an internal plan.io issue https://opendataservices.plan.io/issues/19384. |
[Related issue now on the BODS agile board: http://bods.opendataservices.coop/redmine/issues/436] |
Minor text improvement suggestion: instead of "'xxxx' is too short", have "'statementID 'xxxx' is too short" (If we try to get a field name into all Error Descriptions, users can glance down the Error Description column and see in a one-er which fields are causing problems.) |
These are just the easiest changes to make. https://docs.google.com/document/d/1U3e_b-ZaYnx6QEuCSz03Di3lzof7iPDTP8OpSgZyFU8/edit#
This issue has had the work on theming and rewording validation errors added to it.
Here's a dev instance with a specially crafted file to show all the errors: |
This reverts commit cf824e8.
This will allow individual project libraries (e.g. lib-cove-bods) to rewrite their own error messages more easily.
I've refactored the work that links to this issues. I've split out the oneOf work, that has been merged in these two PRs:
I've moved the validation message changes into lib-cove-bods, although that requires some changes to lib-cove to put more information into the error JSON. |
No description provided.
The text was updated successfully, but these errors were encountered: