Handle unset ref when creating new records #526
Merged
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.
Hi,
I found a small bug in the updated
VariantHeader.new_record
method. When setting the record's initial attributes, the setters' calls tobcf_sync_end
raise an exception becauserecord.ref
isNone
.I added a quick check in
bcf_sync_end
to handle this case. I think settingref_len
to 0 prior to the INFO/END deletion shouldn't have any side effects, since a new record shouldn't have any alleles or a set END anyways.This bug could also be solved by setting
ref
before setting the remaining attributes innew_record
, but I wasn't sure what the desired default would be forref
(or if it would be a good idea to force a default).