search

plouc / nivo

nivo provides a rich set of dataviz components, built on top of the awesome d3 and React libraries
https://nivo.rocks
MIT License
13.08k stars 1.02k forks source link

Tooltips are not consistent for all components #745

Closed taschetto closed 3 years ago

taschetto commented 4 years ago

Is your feature request related to a problem? Please describe. It is not possible to render a custom tooltip within a Calendar day without wrapping it with a BasicTooltip (https://github.com/plouc/nivo/blob/master/packages/calendar/src/CalendarDay.js#L92-L104).

Describe the solution you'd like We should be able to use a custom component alone, without the need to wrap it with a BasicTooltip, just like the Line/Mesh tooltip (https://github.com/plouc/nivo/blob/master/packages/line/src/Mesh.js#L43-L47).

Describe alternatives you've considered I haven't found an alternative.

Additional context

Custom tooltip being used with line charts Custom tooltip being used with line charts

The same tooltip being used with calendars, wrapped inside a BasicTooltip The same tooltip being used with calendars, wrapped inside a BasicTooltip

plouc commented 4 years ago

That's also the case for scatterplot, see https://github.com/plouc/nivo/issues/754

plouc commented 4 years ago

@taschetto I took the liberty to rename this issue instead of having one for each component type behaving differently.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

ianstormtaylor commented 3 years ago

@plouc I think this same issue affected the <ResponsiveTreemap>? I'd like to have the same tooltip behavior from line charts to have complete control over the rendering, but it's getting wrapped in an extra box.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

stale[bot] commented 3 years ago

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!