Philippe Rivière
Philippe Rivière
The *scale*.unknown option can be used to this effect — [examples](https://github.com/observablehq/plot/issues/446#issuecomment-927687059).
This would now happen, I guess, in the default filter https://github.com/observablehq/plot/blob/9d9ba917b5eb3f58e35b81e6555f3565ecffe8eb/src/plot.js#L291 . However with each warning we need to indicate a way to fix the situation, and in this case...
rebased
I'll do that. The goal of the formatting changes was to produce an output with consistent alignement.
Forgot to mention that a solution is to avoid doing the transform, and use e.g.: ``` Plot.dotX(agediff, { x: "age_difference", stroke: null, // don't display any mark sort: {fy: "x",...
Can you share a notebook? When you use `sort: { y: "x", reverse: true, limit: 20 }` inside a mark's options, the "x" part must refer to an existing channel...
Sorry I should have mentioned here that I made a prototype “reticule” plugin (in July 2021) to address this: https://observablehq.com/@fil/reticule-plot-plugin
I think https://observablehq.com/@fil/observable-plot-marimekko-fork is the best current effort. It has a single API entry point (transform): > marimekko({ sequence: "xy", anchor: "middle", x…, y…, value:…, ...options}) Examples show how to...
The example is ready to merge and publish. Is this something we'd want to support as an official Plot.marimekko transform?
I'm struggling a bit with this idea; it seems we would need two marks, one "fake" that does aggregation and sorts the color domain, and the unaggregated scatterplot. But then...