Refactor internal data structures of seqvar query
schema
#374
Labels
enhancement
New feature or request
seqvar query
schema
#374
Is your feature request related to a problem? Please describe.
The
seqvar query
schema data structures are pretty flat. We should structure them more deeply to prevent dozens of attributes. The main offenders areCaseQuery
,SequenceVariant
(not part of query, but internal data structure)Describe the solution you'd like
For
CaseQuery
:consequences
..genotype
- keeptranscripts_coding
,transcripts_noncoding
,max_exon_dist
- move toTranscriptRelated
var_type_*
- move toVariantTypeRelated
gene_allowlist
,genomic_regions
- move toLocusRelated
require_in_clinvar
,clinvar_*
- move toClinvarRelated
gnomad_*
,helixmtdb_*
- move toPopulationFrequencyRelated
inhouse_*
- move toInhouseFrequencyRelated
For
SequenceVariant
:chrom
..ann_fields
- keepgnomad_exomes_an
..helix_het
- move toPopulationFrequencies
struct, renamehelix_*
tohelixmtdb_*
inhouse_an
..inhouse_hemi
- move toInhouseFrequencies
structcall_info
- keep, move up behindann_fields
Describe alternatives you've considered
N/A
Additional context
seqvar query
query schema and use protobuf for input #373The text was updated successfully, but these errors were encountered: