Forwarding the data object rather than its parent to pieChart's title fu... #757
Conversation
|
Oh d'oh, I did not build or look into testing the change... still waiting on |
* master: (57 commits) artifacts; update stock fixture update version more churn will the doc artifact churn never end? more doc artifacts artifacts from updated documentation tools grow bars upward propagate transition duration to d3.behavior.zoom object update stock fixture also test for exactly one title per dot remove extra `fill` add test for dc-js#742 remove superfluous redraw add missing emails to AUTHORS add recently-merged PR authors update doc to match dc-js#744 artifacts s/object/function/ artifacts add optional selector argument to dc.utils.appendOrSelect ...
|
Hmm, I wonder how GitHub would handle me moving this commit back so that I can rebase instead of the merge... easy enough to do it in another branch, but I'm gonna experiment on this one to see if we can salvage it. |
|
For reference, I deleted the branch and re-pushed it one commit back (the merge commit). GitHub automatically closed the Issue. Although the branch is now there and a new issue was successfully created, this one is unable to be reopened with a tool tip dialog stating that the branch was So good behavior, but I think it would be even nicer if it would let us just kind of "clear out" and re-purpose this one. |
|
Weird, I'm surprised by that. Pretty sure I have done that in the past. Oh well, |
...nction in reference to issue #755