james hadfield

This should be improved for sure - thanks for making this issue! There are quite a few tip-related issues which I'll try to bundle together and tackle shortly.

Development was happening at https://github.com/nextstrain/ncov/pull/711 but it has stalled a bit

This was implemented in #1523 however this required all dates to be numeric. I'll leave this issue here but rename it to indicate that we wish to allow YYYY-MM-DD dates

👍 this would be especially helpful for temporal scales (e.g. "report date"), were we to have temporal scales in auspice 😉 Are you suggesting the dataset JSON defines bins, which...

I would very much like it too! Currently filters can be enabled for continuous variables: every single value (on the tree) will be represented in the dropdown, and the ordering...

Tangentially, there would be value in allowing these hardcoded paths to be modified at compile time by auspice customisations. This is already possible for the `/charon` API address ([code here](https://github.com/nextstrain/auspice/blob/master/src/util/globals.js#L140-L151),...

> which I guess should be changed to also use the server address It would be nice to allow customisations of this. The javascript bundles (`./dist/*js` )are static and this...

Also documented in #735 -- would be great to see augur clades improved :)

Oh that could be it for sure -- react not reconciling the DOM properly due to duplicate keys.

Jover is correct on why this is happening. As for solutions, if only one of `X_tree.json` and `X_meta.json` exist we could assume it's a v2 dataset. I don't see many...