Sam Jones

imo the reason to hesitate here, is open source projects often die the death of a thousand props... why Kent C. Dodds describes the reasons for "inverson of control" https://kentcdodds.com/blog/inversion-of-control...

The same could be said of the automatic rotation, actually. You measure the space your chart is in, set a threshold for number of ticks per number of pixels, and...

If it were me making a roadmap, I'd say, auto-rotate, sure, but we need auto-margin, first. auto-rotate, auto-truncate, and auto-margin all together would be slick for unruly data-sets, esp. unruly...

Would love to see this. Seems like keeping it inside the current viewport, so it adjusts its position instead of getting cut off, would solve this most of the time....

@jamesarosen yes, a portal would be better for when the edge of the chart is the problem, but the tooltip still needs to measure against the viewport to adjust its...

@OsmelSynData unfortunately the workaround for me was to postpone upgrading Nivo. We are still on 0.69.1. I wonder if some dependency graph too like https://github.com/pahen/madge could point to where a...

@marvinruder this is a great insight into the problem. Thank you for the time spent digging into this!

running into something similar, but only if I'm consuming typescript from within `node_modules` (in my case, peer scoped packages, npm linked together.)

We use TS, and have used the uncurried version almost exclusively, and have not had any problems, I guess because we aren't using middleware that requires it. We tend to...

@dbritto-dev we aren't currying, but its fine because we aren't using middle-wares. It seems like some middle-wares require it.