D3 v6 updates - Fixes #4 #7
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Open
|
Thank you very much, for now, I will keep this open (for others to find), once I'll find a time (have many things to do in my queue), I'll review this PR, will merge it, and publish a new version |
|
Hi. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In v6 of d3, events were updated to remove the global "d3.event" and pass the event content itself. This pull request updates the data-driven-range-slider to use the new syntax.
Updated version to 2.0.0 since you now need a specific version of d3. Updated to peerDependency so projects won't have multiple versions of d3 installed in node_modules.