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
I generally like the new behavior where visualization state is preserved when switching between datasets via the dropdown. Ie, if I'm at https://nextstrain.org/zika?l=clock and switch to ebola I arrive at https://nextstrain.org/ebola?l=clock. However, if the original visualization state doesn't exist in the target dataset then the app crashes out to 404. For example, if you start at https://nextstrain.org/zika?c=gt-NS1_349 and switch to ebola then the get the crash as ebola doesn't have NS1 to color by.
I don't know the best treatment for this. One option would be to return to the previous behavior of nuking state, but this is bad for things like panel grid. Fixing the crash on genotype color by seems like an obvious first step.
The text was updated successfully, but these errors were encountered:
Aha... This wasn't intentional - but yes, it's nice in some situations!
Geographic resolution & colorBy are "dataset specific" (as opposed to grid etc) so perhaps these should be nuked on dataset change... Other things work but remain in the URL (e.g. having the frequency panel in the URL and going to zika doesn't raise any errors, but the frequency panel is still specified in the URL, which isn't correct)
@jameshadfield ---
I generally like the new behavior where visualization state is preserved when switching between datasets via the dropdown. Ie, if I'm at https://nextstrain.org/zika?l=clock and switch to ebola I arrive at https://nextstrain.org/ebola?l=clock. However, if the original visualization state doesn't exist in the target dataset then the app crashes out to 404. For example, if you start at https://nextstrain.org/zika?c=gt-NS1_349 and switch to ebola then the get the crash as ebola doesn't have
NS1
to color by.Actually... for non-genotype color bys you don't get a 404, but it's still unexpected behavior. For example, go from https://nextstrain.org/WNV/NA?c=wnv_strain and select zika and you end up at https://nextstrain.org/zika?c=wnv_strain, which then shows coloring by date.
This issue exists for geo resolutions in addition to color bys. For example, https://nextstrain.org/zika?r=region switches to https://nextstrain.org/ebola?r=region, which doesn't exist.
I don't know the best treatment for this. One option would be to return to the previous behavior of nuking state, but this is bad for things like panel grid. Fixing the crash on genotype color by seems like an obvious first step.
The text was updated successfully, but these errors were encountered: