VEP: Improve documentation on SV support #799
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nakib103
requested changes
Jun 28, 2024
There was a problem hiding this comment.
Looks good, I have some small suggestions.
Also, @nuno-agostinho,
Would it better to have the http://wp-np2-11.ebi.ac.uk:6070/info/docs/tools/vep/vep_formats.html#sv at the end of Input section with h2 header type like others? As it has multiple input format supported it does not need to be under VCF section, and with h2, a link in the side nav would be better.
Co-authored-by: Syed Nakib Hossain <snhossain@ebi.ac.uk>
|
Thanks @nakib103, moved the SV section as a H2 section to the end of Input. What do you think? |
nakib103
approved these changes
Jun 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ENSVAR-6222
Testing
Check changes in my sandbox: