✅ Deploy Preview forsvelteplot ready!

Name	Link
🔨 Latest commit	8720aa0
🔍 Latest deploy log	https://app.netlify.com/projects/svelteplot/deploys/6919c057f4acdc0008cabb75
😎 Deploy Preview	https://deploy-preview-70--svelteplot.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to yourNetlify project configuration.

Awesome.

As I'm writing this section,@gka, I find it weird that the current available transforms are inside a "Map" category. As perd3-array's documentation, this lies under "Summarizing Data".

I would expect a Map transformer to receive a callback function that transforms the data in some way. For example, taking all Athlete names and converting them to a smaller format:

"Michael Phelps" → "M. Phelps"
"Aaron Brown" → "A. Brown"

This is a small example but I think it gets the point across of what I'm trying to say.

Maybe the current "Map" section could be called "Summarize", a series of transformations to summarize the data, in which we can now include the rest of the available methods, like sum, min, max, and so on.

Maybe I'm understanding it wrong, though! Would love if you could shed some light on this topic!

Maybe the current "Map" section could be called "Summarize", a series of transformations to summarize the data, in which we can now include the rest of the available methods, like sum, min, max, and so on.

I'd expect amapfunction to transform a list of values to a list of the same length, but containing modified values.

I'd expect asummarize function to transform a list of values to a single value.

Cumsum, rank and quantile transform a list of values to another list of values, so I think they're more appropriately described asmap thansummarize.

However, I would generally expect amap function to act on each value individually. There might be an alternative name that is clearer, butMap is what Observable Plot uses and it woud be good to maintain API compatability.

However, I would generally expect a map function to act on each value individually. There might be an alternative name that is clearer, but Map is what Observable Plot uses and it woud be good to maintain API compatability.

I guess this is the core issue: it's a cumsum is a Map because it receives an array and outputs an array of the same size, but output is dependent on all elements

GlobalMap, or something along those lines could work. I do agree, though, to stick to Observable's API naming. In fact, I was trying to stick with d3's!