4 ms·

These two posts by the creator, Mike Bostock, sound similar to what the gp described. https://bost.ocks.org/mike/join/ https://bost.ocks.org/mike/join/ https:/

• jcheng 6y ago
  That first one is what did it for me, years ago—IMHO it’s not even worth trying to form a mental model of d3 until after you’ve read that.
• tonto 6y ago
  The data join thing is interesting. I'd be curious about other future opportunities for d3 to sync up more with react. Posts like this [0] show that d3 can "just generate the path" and then at that point you can use different renderers like React e.g. return <path d={line(data)}/>. It is more limited doing it this way but more ties into the react model would be wonderful https://observablehq.com/@d3/d3-line https://observablehq.com/@d3/d3-line
  • jwilber 6y ago
    I don’t have any public codebase examples at hand, but what we’ve done at work also works quite well: basically we implement our D3 charts as a class with methods corresponding to desired lifecycle events. We then create a Component wrapper around said class and call the methods during their corresponding lifecycle events. (Idk how confusing or not that was but I wish I had a repo to share to make it clearer). There’s also a book I read while ago from Swizec Teller on d3 + react integration[0]. It may be dated by now as it’s been some time since I last read it, but it’s worth looking into! [0] https://leanpub.com/reactd3jses6 https://leanpub.com/reactd3jses6