-
Notifications
You must be signed in to change notification settings - Fork 4
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
EVA-3525 update validation report #39
EVA-3525 update validation report #39
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.
Some implementation suggestions, the HTML report looks way better though 👍
except Exception as e: | ||
self.error('Error building Validation Report : Error getting info from metadata file' + str(e)) | ||
else: | ||
self.error('Error building validation report : Metadata file not present') |
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.
I think this does almost exactly the same thing as this logic in the fasta check. It should be possible to either extract and re-use that logic, or adjust the results from that check and then use those directly in the report (currently looks like this - I think it just needs the vcf file listing).
If we're worried about the fasta check not being run but still wanting to include the summary, I guess code reuse is the best bet. But #38 should help make that one more reliable anyway.
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.
As discussed, the refactoring comment is optional and can be done later if needed 👍
Also added icon for showing list is expandable