Skip to content

Conversation

@anju24
Copy link

@anju24 anju24 commented Sep 4, 2025

Relates to #791

@github-actions
Copy link

This issue is stale because it has been open 180 days with no activity.
Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale Issue is stale and subject to automatic closing label Sep 13, 2025
@davmlaw
Copy link
Contributor

davmlaw commented Oct 9, 2025

I kept the logic changes in main (for uncertainty), while keeping typing changes from 791-type-hints

I think I messed up my git origin so will put this on my own repo/branch then pull request into anju24's repo branch to update pull request

There were a few issues with the type hints:

normalizer.py - boundary can return float('inf') not just tuple[int, int] as can _get_tgt_length so just removed those annotations

validator.py - Changed strict: bool = None to strict: bool | None = None. Line 86 - validate(var: bool = None) was wrong (should have been var: SequenceVariant)

variant mapper - used "hgvs.intervalmapper.Interval" - I don't think it should have been this one (there are 2) - deleted it

@github-actions github-actions bot removed the stale Issue is stale and subject to automatic closing label Oct 9, 2025
@davmlaw
Copy link
Contributor

davmlaw commented Oct 9, 2025

I pushed to wrong place and it ended up in this repo's branch: https://github.com/biocommons/hgvs/tree/791-type-hints

Changes vs main: main...791-type-hints

I was able to fix conflicts with main, though when I tried to get it back onto @anju24 pull request, it still ends up with merge conflicts. I suspect this may be due to the auto formatting?

Perhaps it would be easier to make a new pull request from that other branch?

@github-actions
Copy link

This issue is stale because it has been open 180 days with no activity.
Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale Issue is stale and subject to automatic closing label Oct 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale Issue is stale and subject to automatic closing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants