-
Notifications
You must be signed in to change notification settings - Fork 516
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
Feature Suggestion: Include a Reason When Constraints Cannot Be Applied #2630
Feature Suggestion: Include a Reason When Constraints Cannot Be Applied #2630
Conversation
Signed-off-by: Robert Simpson <[email protected]>
Signed-off-by: Robert Simpson <[email protected]>
Signed-off-by: Robert Simpson <[email protected]>
Signed-off-by: Robert Simpson <[email protected]>
Signed-off-by: Robert Simpson <[email protected]>
Signed-off-by: Robert Simpson <[email protected]>
Signed-off-by: Robert Simpson <[email protected]>
I like this suggestion; however, the implementation is a little less "Pythonic" than it ought to be. First, the nitpicky comment: variables should be snake_case ( |
Signed-off-by: Robert Simpson <[email protected]>
Signed-off-by: Robert Simpson <[email protected]>
… into feature/apply-constraint-fail-reason
Kudos, SonarCloud Quality Gate passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution and for the prompt turn around on feedback!
@dbluhm And, likewise, thanks for the quick feedback and merge. Much appreciated. |
When the verifier agent is unable to apply a constraint filter, it would be helpful for the Problem Report to include a reason why it failed. For example, instead of:
... the message could include the reason that the constraint could not be applied, with the specific path or item that did not match. For example:
This indicates that the field indicated in the message was not found in the Reveal Document or the full Credential.
or
This indicates that the "part2" property found in the Reveal Document under "$.credentialSubject.part1" was not found in the list of fields in the constraints.