Mike Bostock

It’s possible to do this with some hacky CSS, but it’s pretty brittle and I expect it would break months from now with some future VitePress release. So I filed...

A quick note because I’m not sure I have the bandwidth to work on this now, but I think this should work more like the implicit centroid transform for the...

A challenge I have reviewing this PR is that I don’t feel we’ve developed principles to guide these changes. This “fixes” the **tip** option and/or the pointer transform for the...

For now I think the simpler contract for marks would be to provide a “representative point” (or point of interest), since that this point could be used by the pointer...

Maybe having the pointer transform and tip mark understand the _geometry_ channel could be simpler? I want to try that too.

Ah, okay, interesting. So in this PR you use a new _polygon_ channel rather than the existing _geometry_ channel, but you also redefine the _x_ and _y_ channels to contain...

We could allow the project config to register additional code transforms for `getLiveSource`? https://github.com/observablehq/framework/blob/97aa3cedfbc006490e0d0df630a22f35003aeb5f/src/markdown.ts#L52-L66

@srenatus Tracking PRQL separately with #1075; some progress in #1078.

An initial thought… Actual difficulty is unique to each reader because it depends on the reader’s own experience and way of thinking. Regardless of what we estimate to be easy...

I would love for us to do decimation automatically (and transparently) when rendering areas and lines. (Even if only for the _linear_ curve… and maybe we can make it work...