Closed abought closed 2 years ago
In the current form this is a very unbounded problem. It might make more sense for individual consuming sites to expose the options relevant to their specific usage. Closing this form of ticket as it is too broad to be directly actionable for the most common use cases.
Most deployments of LocusZoom rely on the developer to choose the display options up front. This works well for a website that browses a known, pre-selected type of data.
For our reusable "bring your own data" tools, the defaults are not universally appropriate: eg a user may want a different line of significance cutoff for eQTLs vs GWAS results.
We should provide UI to control a few common display options. We do not want infinite buttons; some thought should be given to which options are most useful, and how to provide context-sensitive configuration.
Examples:
Knowing which settings are most important to change would help create focus on the most useful and user-friendly options.