-
Notifications
You must be signed in to change notification settings - Fork 13
Return validation reports #579
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
Conversation
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.
Just a minor comment but this looks great! THANKS a ton and a million sorry for the delayed review!
sorry @matentzn I need a re-review, since there was a test I hadn't noticed had failed; related to checking the validate function returned none, and now it returns something that we can actually check in more depth! |
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 test fixes
I'm currently trying to use
sssom.io.validate_path
to check that SSSOM files generated by SeMRA are valid, but it's very difficult to get access to the results of validation programmatically. There should be some logging output to stderr, but this isn't so helpful in a unit testing environment.This PR makes the validation functions return the reports generated by LinkML, so they can be returned and used downstream.
This PR also operationalizes the default validator list, meaning you don't have to import them or know what they are to get this function up and running.
Blocked by #580
Alternative to #387, but that PR uses custom results instead of returning the LinkML objects