As a follow-on to #40, inspired by @mbostock, perhaps it would be sensible to rename the methods:
create -> enter
render -> update
destroy -> exit
The reason why the names were create, render, destroy in the first place is that they do different things from the original enter, update, exit, and I didn't want to introduce confusion around overloading these names. However, they are indeed invoked within those very phases of the general update pattern, and it's clear enough that they are invoked on instance of d3.component, not selections. Maybe it would make sense to use these names after all.
This is how the API would look after the name change:
As a follow-on to #40, inspired by @mbostock, perhaps it would be sensible to rename the methods:
create
->enter
render
->update
destroy
->exit
The reason why the names were
create
,render
,destroy
in the first place is that they do different things from the originalenter
,update
,exit
, and I didn't want to introduce confusion around overloading these names. However, they are indeed invoked within those very phases of the general update pattern, and it's clear enough that they are invoked on instance ofd3.component
, not selections. Maybe it would make sense to use these names after all.This is how the API would look after the name change:
Any thoughts?