The workflow determines optimal bin widths for use in the subset tab. It uses the plot.data R package to do this, which guarantees we remain consistent between the subset and viz tabs while improving performance.
This issue is a proposal to do the same for the binSlider specs.
Currently, determining bin slider min, max and step values is done slightly differently for the subset and viz tabs, w similar but not identical logic existing in both plot.data and web-eda. This not only means that behavior is slightly different in the two places, but also that changes to that behavior have to be implemented in two places.
I didnt want to drop this into EdaLoadingIssues in case people wanted to discuss first.
The workflow determines optimal bin widths for use in the subset tab. It uses the plot.data R package to do this, which guarantees we remain consistent between the subset and viz tabs while improving performance.
This issue is a proposal to do the same for the binSlider specs.
Currently, determining bin slider min, max and step values is done slightly differently for the subset and viz tabs, w similar but not identical logic existing in both plot.data and web-eda. This not only means that behavior is slightly different in the two places, but also that changes to that behavior have to be implemented in two places.
I didnt want to drop this into EdaLoadingIssues in case people wanted to discuss first.