You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that collection is an option to select in the sidebar's Color By dropdown
Possible solution
Differing versions of auspice (2.17.0 in nextstrain.org and 2.12.0 in auspice.us) are my best guess as to the difference in behavior - several hundred commits in auspice separate the two. One way to solve this is to try and find the commit that broke it, another way is more directly debugging the current code.
Your environment: if browsing Nextstrain online
Operating system: macOS High Sierra 10.13.4 (17E199)
Browser: Chrome Version 83.0.4103.106 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered:
It used to (and still should) work in auspice by itself, so bisecting (perhaps from 2.12 which auspice.us is running) should identify the commit which breaks it.
Bisecting indicates this is 20d8439, which makes sense: the new coloring is being correctly added to the redux state as an available option, but the drop-down is not being updated due to the shouldComponentUpdate code introduced in that commit. This also explains why the TSV-derived color-by option magically appears in the dropdown once you change the color-by to any one of the original options.
Current Behavior
From @trvrb :
Expected behavior
Drag and drop should work to add a color by option to the dropdown upon dropping and parsing a TSV. This works on auspice.us
How to reproduce
Reproduce bug:
auspice view --datasetDir examples
and go tohttp://localhost:4000/minimal/v2
collection
is not an option to select in the sidebar's Color By dropdownReproduce correct behavior:
collection
is an option to select in the sidebar's Color By dropdownPossible solution
Differing versions of auspice (2.17.0 in nextstrain.org and 2.12.0 in auspice.us) are my best guess as to the difference in behavior - several hundred commits in auspice separate the two. One way to solve this is to try and find the commit that broke it, another way is more directly debugging the current code.
Your environment: if browsing Nextstrain online
The text was updated successfully, but these errors were encountered: