Fix/properly parse genbank location #16
Merged
Conversation
This file contains hidden or 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
mcolpus
approved these changes
Nov 20, 2025
mcolpus
left a comment
mcolpus
left a comment
There was a problem hiding this comment.
Looks good. Code is quite complex not gonna lie, but tests continue to pass on the previous examples and I've tried running it locally on the provided tricky reference
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.
Expands which genbank files can be properly parsed, including most NTMs.
complementandjoindefinitions in genbank files are correctly parsedINCOMPLETE_<original gene name>in cases where coding genes are defined without the correct number of nucleotides for codons.