niagads/niagads-viz-js

NIAGADS visualizations

niagads-viz-js's Issues

promote accessors

move accessors outside of tables
potentially rename to reflect more generic usage

table: row select

• add option for user to enable row-select (via displayed check boxes)

• tie an action to the select; will need to discuss use cases to plan

table: revisit sorting

not all specialized cases sort correctly; revisit after accessors are revised

make LocusZoom record link outs dynamic

currently implemented as relative links to the GenomicsDB

need to be able to make them dynamic (supply baseUrl as parameter)

migrate react-tables to v8

Migrate the Table and related components from react-tables v7 to v8.

Migration guide available here: https://tanstack.com/table/v8/docs/guide/migrating

Focus on:

• instantiating and rendering the table
• pagination
• show/hide columns
• column accessors

Advanced - may need to be elevated to their own tasks

• sorting (basic / custom sorts from GenomicsDB TODO later)
• row selection
• column filtering (basic / custom filters from GenomicsDB TODO later)

table: improve look

Format the tables for a nicer look, includes:

• add CSS for cell, row, and header formatting
• write header renderer; should include info bubbles as needed
• table container (see related tooltip issue #13)
• pagination
• scrolling on x-overflow?

table: export / download

add exporting of table contents

used https://www.npmjs.com/package/react-csv successfully in other projects

but may want to look elsewhere as we would want to support:

• json
• xlsx
• csv
• xml

table-filters: global (text) filter

• create global (text) filter for the table
• should ignore non-text (integer / float / boolean) columns

table: table toolbar

• toolbar component above table should contain the global-text filter and action buttons for export, add/remove columns, filters, and info button

from the existing GenomicsDB tables:

table: info / about table modal

• model after GenomicsDB to add table usage instructions to the table object
• user should be able to pass additional information via the table.options (e.g., behavior on row selection, table title, description, data sources)

table: tooltips being cut off by table container

possible solution : https://stackoverflow.com/a/611098

make tables work generically

• remove Dataset interface from types
• create optional component argument allowing users to pass a type def (interface) that defines a table row
• if optional arg is undefined, allow generic typed row