-
Notifications
You must be signed in to change notification settings - Fork 7
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
As a user, I want validate to report the value found on a valid-list failure #760
Comments
@rgdeen this is a schematron rule that validate doesn't have any real control over, so this is something we can try to support in schematron in the future. Unfortunately, we cannot retrofit this into past IM releases. |
@rgdeen that being said, that line number should also help in tracking down where this is in the label. |
Ah. So the error is coming out of the schematron engine, not validate per se. Okay. This is not a big deal, just thought it would be an easy improvement... if not, don't worry about it. I guess we could pass a request along to the schematron folks but up to you if it's worth the trouble. Note that it was a general comment, not related to that specific attribute (it's just an example) so no need to update the schematron rule just for that item. (I'm not sure if you could, anyway). I use the line number a lot. |
Checked for duplicates
Yes - I've already checked
π§βπ¬ User Persona(s)
data engineer
πͺ Motivation
When we have an attribute with a valid list, and the value is not in the list, we get an error message such as the following:
It would be very helpful if it also reported what value it actually found (in this case, "Sun"). That way I could easily scan the validate output to find all the bad values and fix them at once, instead of having to go to each product individually to look up what's in the label. I'd wanted this feature several times in the past...
π Additional Details
validate version 2.1.4
Acceptance Criteria
Given
When I perform
Then I expect
βοΈ Engineering Details
No response
The text was updated successfully, but these errors were encountered: