-
Notifications
You must be signed in to change notification settings - Fork 130
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
augur validate output isn't easily interpretable #440
Comments
Distinguishes between schema validation and internal consistency (e.g. data) checks and includes filenames in top-level messages so the subject is clear. Resolves #440.
Hi @crashfrog, thanks for this report. I agree the messages here are pretty confusing. Right now the validation code is a bit ad-hoc and messaging isn't unified. I've tried to clean up and clarify some of that in #441. Although it's totally unclear, your file did validate, but there were some non-critical warnings you might want to resolve regarding The nodes probably lacked those traits because although your metadata file given to |
Distinguishes between schema validation and internal consistency (e.g. data) checks and includes filenames in top-level messages so the subject is clear. Resolves #440.
Thanks, that's helpful. I'll review the documentation you linked, I hadn't seen that before. |
Hard to make sense of this output. Did validation succeed, or fail? (It exited with code
0
.) If it failed what was the failure? Are the warnings actually meant to be failures? Why don'tlocation
orauthor
appear as properties on the nodes if they're part of the metadata file given toaugur export
?The text was updated successfully, but these errors were encountered: