#6288 - incorrect number in sequence #6668
Open
+179
−30
Conversation
This file contains 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
lmhs
force-pushed
the
6288-incorrect-number-in-sequence
branch
from
93c30f6 to
61b4e8f
Compare
This was
linked to
issues
Mar 19, 2025
- Linker nodes can be inside subchain - they shouldn't have number, but nodes right before and right after them can have number (node index which ignores the linker nodes coming before it) - optimised counterNumber property in case different conditions have same result -
lmhs
force-pushed
the
6288-incorrect-number-in-sequence
branch
from
e021c7e to
17910e5
Compare
…g for phosphate, fixed numbering for antisense nodes
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.
How the feature works? / How did you fix the issue?
Limit number display to:
Don't display number:
Check list
#1234 – issue name