-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Add is_exonic field to transcript segment output
#423
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
Conversation
zealws
left a comment
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.
Looks good to me!
| genomic_location: SequenceLocation = Field( | ||
| ..., description="The genomic position of a transcript segment." | ||
| ) | ||
| is_exonic: bool = Field( |
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.
Kind of related to this PR... If the genomic location should only contain one of: start or end, then we should add a validator for this (separate issue).
The reason why I was thinking is if there's ever a case where the location would be a region that could include both exon/intron data.
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.
That makes sense to me. seg_start and seg_end each should only contain one coordinate as they describe either the start or end of the transcript segment. To confirm, is this something we could add in a different PR?
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.
Yes, create an issue for this
Closes #422
A new field called
is_exonicis added which indicates whether or not the position at the start or end of a transcript segment occurs on an exon.