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'm unable to specify multiple inputs’ values for the same selection.
Repro: Add value: fencing and value: female to the first two menus (here and here) in specs/yaml/athletes.yaml and load the “Athletes” example in the dev server. See that only the first menu has its value pre-selected:
The text was updated successfully, but these errors were encountered:
Thanks! I suspect the shared selection is updating with the first value and that this is then interfering with the second value being properly added. Such values should interfere when the selection resolution strategy is single, but not in this case where we have a standard intersect selection. I'll look into it.
PR #403 fixes this issue: initial values should be properly reflected in the menu and populated in the selection. It will be included in the next release.
However, note that setting initial values can lead to other wrinkles if you are using Fixed domains. Fixed domains initialize to the first data seen and are then locked in place. So if you start with filtered data, you will get locked-in domains over the filtered ranges. So for now you may want to "hardwire" scale domains to desired values to have the scales reflect the full range of the data and remain fixed.
I'm unable to specify multiple inputs’ values for the same selection.
Repro: Add
value: fencing
andvalue: female
to the first two menus (here and here) inspecs/yaml/athletes.yaml
and load the “Athletes” example in the dev server. See that only the first menu has its value pre-selected:The text was updated successfully, but these errors were encountered: