-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow custom legendNode for markers #2432
Conversation
Allow `legendNode` props for finer control over legend customization for markers
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 16ecb26:
|
@plouc Can I do something to help this PR be merged ? |
lets aprovve this PR @plouc ! |
Up'ing this, how can I help? |
@Bigood, sorry for the late reply, the PR needs to be rebased, I think it would be good to add a test for it as well, maybe not in the core though, it's probably better to test this on a chart supporting markers. |
@plouc Right on time, as requested here is a test on Line on updated codebase. I don't know what to do to solve Vercel's deploy failure though. Is that ok? |
@plouc I don't mean to be pushy, but I have a time window to edit this PR if there's something to be done. Otherwise, if everything's mergeable, could you give an estimation of when you'd have time to push the button ? I'd personally like to upgrade my version of nivo on my project, but I can't for the moment as I heavily depend on this functionality (I dangerously use the package build by codesandbox, and can't yet find a way to use patch-package properly to patch the builded version easily). |
Vercel ran fine, for codesandbox, it's unrelated. |
@Bigood, could you please run prettier? |
Allow
legendNode
props on markers for finer control over legend.Usecases :
Usage :
Expected result :
Codechanges :
Two lines changed to bypass legendNode creation with legend text.
Doesn't break any existing functionality, and seams easy to maintain across updates.