SACGF / SACGF/variantgrid

Can no longer classify invalid HGVS (one we can't resolve)

Open
#810 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
30
Forks
3
Avg merge
9h 22m
Merged PRs (30d)
40

Description

The classifications page has a HGVS entry text box, where you can enter HGVS that fails (eg NM_007300.4:c.2902_2959inv) and classify against it.

This was done by passing the "classify" field to the search, which has special case.

I think this was broken in the conversion to crispy forms - it no longer renders hidden fields so the "classify" hidden field is not passed to the search form anymore

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the classifications page's HGVS entry text box and follow how it submits to the search form. Check the crispy forms conversion and the special-case handling of the "classify" field; done means an otherwise unresolvable HGVS such as NM_007300.4:c.2902_2959inv can be classified successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
full-stack
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.