-
Notifications
You must be signed in to change notification settings - Fork 67
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
allow-warnings and allow-infos need a unit test #126
Comments
The weekend's starting for me, but I'll try to get something posted Monday. Apologies for the trouble. |
Glancing at the README, I see I missed updating the "Front-page" documentation. I'll pick that up in the resolving PR. |
This test demonstrates the current implementation state fails. A follow-on patch will correct the issue. References: * RDFLib#126 * The general style of this test was adapted from `/test/issues/test_96.py`. Signed-off-by: Alex Nelson <[email protected]>
This lets `allow_infos` to influence the `all_warn` variable appropriately. With this patch, the new `test_126.py` now passes. References: * RDFLib#126 Signed-off-by: Alex Nelson <[email protected]>
This patch applies no creative input. `pyshacl -h` was run in an 80x24 window, and the command output was copy-pasted into the corresponding README section. This patch was instigated by adding the flag for `--allow-infos`. References: * RDFLib#126 Signed-off-by: Alex Nelson <[email protected]>
References: * RDFLib#126 Signed-off-by: Alex Nelson <[email protected]>
@ashleysommer , PRs 127 and 128 are ready for your review. When both are merged, I'm fine with closing this Issue. You had said in PR 121 that you were going to add corresponding flags with non-plural spellings. Did you still intend to do that before releasing? |
@ajnelson-nist |
@ashleysommer , I found a few cleanup matters, filed in PR 137. |
PR-121 was supposed to enable a result of
sh:conforms true
if onlysh:Info
-level validation results were yielded. A unit test wasn't included in the PR to confirm--allow-infos
worked. I also attempted to trigger--allow-warnings
and didn't get an expected result. A test needs to be provided to confirm both command-line flags work.The text was updated successfully, but these errors were encountered: