Skip to content
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

Autogenerate tables and definition lists #88

Open
pjvandehaar opened this issue May 30, 2017 · 0 comments
Open

Autogenerate tables and definition lists #88

pjvandehaar opened this issue May 30, 2017 · 0 comments

Comments

@pjvandehaar
Copy link
Collaborator

pjvandehaar commented May 30, 2017

autogenerate table columns

(see also #21 #42)

  • Manhattan: per-variant and per-assoc fields
  • [regionLZ, geneLZ] (bottom-table): per-variant (w/o genes?) and per-assoc
  • geneLZ (top-table): all fields
  • top-hits: all fields

for [Manhattan, regionLZ, geneLZ/bottom], linking to gene pages will require phenocode, which must be passed in somehow.

Strategy:

  1. start with conf.parse.fields[].table_underscoretemplate and conf.parse.template_only_fields[].table_underscoretemplate
  2. fill in defaults
    • each entry must end up with head_template, cell_template, inclusion_criteria (just a disjunctive list of fields?).
  3. pass to js via model.table_underscoretemplate
  4. at render time, check which columns to include, render the table header into the page, and pass the row template to streamtable.
    • every page must receive all 3: per-variant, per-assoc, and per-pheno.
      • Manhattan & LZ will store per-pheno at model.const
      • PheWAS will store per-variant at model.const
      • var wrappedtemplater = obj => templater(deepcopy(obj).update(model.const))
    • also, somehow pass color_by_category to the table template on pages that have categories (ie, PheWAS and tophits)?
    • figure out ordering, hiding at various screensizes, and hiding nearest_gene on geneLZ.

autogenerate definition lists

  • [regionLZ, Manhattan]: per-pheno fields
  • PheWAS: per-variant fields

These are just <p>s, so just use templates like .tooltip_underscoretemplate.

Just feed in model.const.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant