Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Allow the use of getSAMString on SAMReadGroupRecord objects #827
Conversation
| +/* | ||
| + * The MIT License | ||
| + * | ||
| + * Copyright (c) 2009 The Broad Institute |
Lenbok
Mar 17, 2017
Contributor
Haha! (Copied an existing test file from the same package as the starting point and the comment was folded in the editor off the bat! I can update if you want)
codecov-io
commented
Mar 16, 2017
•
Codecov Report
@@ Coverage Diff @@
## master #827 +/- ##
===============================================
+ Coverage 64.865% 64.868% +0.002%
- Complexity 7189 7194 +5
===============================================
Files 527 527
Lines 31769 31774 +5
Branches 5424 5424
===============================================
+ Hits 20607 20611 +4
+ Misses 9015 9014 -1
- Partials 2147 2149 +2
Continue to review full report at Codecov.
|
lbergelson
was assigned
by droazen
Mar 21, 2017
|
looks good @Lenbok. This is a good idea. Could you do the same refactoring for the 3 other classes that inherit from AbstractSAMHeaderRecord and add an abstract getSAMString() function to AbstractSAMHeaderRecord? |
|
@Lenbok This seems like a good idea and the implementation + test seems good. It seems like a good idea for all of the other types of header lines as well. If you don't mind, could you make |
|
@yfarjoun, @lbergelson No probs, done. I didn't construct an explicit new test for SAMFileHeader.getSAMString(), as that one is essentially refactored out of the existing clone() method, which already gets called all over the show. |
|
@Lenbok Thanks you! |
Lenbok commentedMar 16, 2017
Description
Fairly minor, this just allows programmatic access to the string representation of a read group, in much the same way as SAMRecord.getSAMString(). AFAIK there currently isn't really a non-convoluted way to get this. This is useful for displaying to the end user a problematic SAM read group.
Checklist