As shown in the screenshots (please see below), if frontend passes binWidth: undefined to backend, then backend returns correct value, binWidth: 1. However, binWidthRange is incorrect, { min: 0.1, max: 0 }, which causes error in Viz control: red border in the second screenshot which means that it has error and the value cannot be changed. Also bin slider shows incorrect range as well. Danielle confirmed that this is a bug at plot.data.
An example test case: qa.vectorbase.org; STUDY: Geolocation visualizations of field-based studies; EDA histogram Viz; Filter: Species -> Aedes; Main variable: count of traps.
This bug was found when addressing https://github.com/VEuPathDB/web-monorepo/issues/959 (closed but has detailed information) and https://github.com/VEuPathDB/web-monorepo/issues/961 (replacing 959): this is possibly address by https://github.com/VEuPathDB/web-monorepo/pull/964.
As shown in the screenshots (please see below), if frontend passes
binWidth: undefinedto backend, then backend returns correct value, binWidth: 1. However,binWidthRangeis incorrect,{ min: 0.1, max: 0 }, which causes error in Viz control: red border in the second screenshot which means that it has error and the value cannot be changed. Also bin slider shows incorrect range as well. Danielle confirmed that this is a bug at plot.data.An example test case: qa.vectorbase.org; STUDY: Geolocation visualizations of field-based studies; EDA histogram Viz; Filter: Species -> Aedes; Main variable: count of traps.