Get rid of d3_tiny
#440
Merged
Get rid of d3_tiny
#440
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
….append(Rpd.unit(node)) everywhere, still some examples do fail
|
Not yet to merge, but to keep users aware it's coming soon. Probably the version will be |
…eems fails to work as before
|
Raised #441 |
…solution to store independent data
|
HTML renderer is working properly now, SVG still fails, though |
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.
Can't stand this inconsistency no more :). Based on #405 and friends.
Issues arise, d3 API changes. Some issues appeared when I updated to
d3.jsfromnpm, some were left there by accident (#439, seems it's about you, my darling).Now d3.js is split in micro-modules and
d3-selectionis actually covers everythingd3_tinydid. Of course it is much larger is size (irony), but who cares nowadays?