Open
Conversation
added 30 commits
February 19, 2026 16:16
…write degenerate in the same flow.
… into tuple_to_dataclass
… into tuple_to_dataclass
… into tuple_to_dataclass
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
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.
Pull Request Details
This pull request replaces tuple-based return values with dictionaries across the crossmapper. This change introduces dictionaries with explicit keys, improving:
For example, instead of:
position, offset, in_cds, in_transcript = func(...)The API now returns:
pos_m = func(...)pos_m['position']pos_m['offset']pos_m['region']pos_m['position_in_codon']Documentation has been updated to reflect these new return types.
Breaking Changes
Functions that previously returned positions in tuples now return dictionaries. This affects downstream code that:
positionvalues without considering its regionTests