Mike Bostock
Mike Bostock
Related feedback from Misha Tsvelik: https://vimeo.com/829300247/91d6c7eeef This issue applies to ticks, and not just tick formats: for example if the data is just integers, then we wouldn’t want to show...
This is pretty much fixed by #1728 for time axes, but we’d need to do something similar to numbers/integers. ~~And also this isn’t fixed for binning, in the sense of...
I got this working in #1790, but messy: ```js : tickFormat === undefined && data && isNumeric(data) && scale.interval?.[intervalDuration] ? format(`.${`${scale.interval?.[intervalDuration] % 1}`.length - 2}f`) ```
This umbrella issue is over a year old. We should close it and re-open more specific issues as needed.
This would be useful for a lot of raster mark applications, too.
(I am not sure the treatment is 100% correct with respect to padding in ordinal scales, but it’s probably “close enough for now” and we can improve it later.)
Probably superseded by #1320 which goes the d.ts route. Close?
I think this is only a bug with the facet channels, right? Normal channels should be transformed consistently; it’s just the facet channels that don’t respect the transforms. I made...
@Fil It should already work if you use the **channels** option to declare an additional channel.
Since 0.6.7 you can shorten slightly too: ```js Plot.plot({ marks: [ Plot.barX(clean_monthly_april, { y: 'title', x: 'activations', channels: {difference: 'difference'}, sort: {y: 'difference'} }) ] }) ```