-
Notifications
You must be signed in to change notification settings - Fork 0
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
hide leading 1 for offset PositionalVariants #17
Comments
Following the issue's description, when a POST request is sent to the GraphKB Api on the '/positionalvariants' route, the create() function is called (pori_graphkb_api/src/repo/commands/create.js), which will eventually lead to the GraphKB Parser : 1- the convertPositionToString() function will provide values for the break1Repr and break2Repr properties: pori_graphkb_parser/src/position.ts Lines 179 to 207 in 139af0d
2- based in part on those properties, the stringifyVariant() function will provide the displayName's value: pori_graphkb_parser/src/variant.ts Lines 206 to 292 in 139af0d
Question: |
Here are the implementation of the 2 proposed solutions: |
From JIRA https://www.bcgsc.ca/jira/browse/KBDEV-990
Problem:
PositionalVariant with a negative offset from the 1st position should hide the position '1' in their displayName as per HGVS standards (https://varnomen.hgvs.org/bg-material/numbering/), which is not the case at the moment.
Ex.:
"CEP72:c.1-2384C>T" should read "CEP72:c.-2384C>T"
Context:
When a PositionalVariant is added to GraphKB (let say through the web client interface, which uses the '/positionalvariants' POST route), the payload doesn't contain a displayName, neither a break1Repr nor a break2Repr. The parser is then used to format these fields.
The text was updated successfully, but these errors were encountered: