You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mbostock
changed the title
Should some of the existing constant properties (e.g., textAnchor) support being data-driven
Should more constant properties (e.g., textAnchor) be specifiable as channels?
Feb 27, 2021
My hot take on this is “no” because you can always fall back to creating marks programmatically as needed, e.g., one Plot.text for right-aligned labels and another for left-aligned labels, with the requisite transform (or filter #138) to control who gets what. My rule of thumb is that if it’s not really a visual encoding of data, meaning if it isn’t intended to communicate information (and you wouldn’t want a corresponding legend or axis) and if there’s only a few values that it could reasonably have (e.g., label orientation) then it’s nice for simplicity for the property to be a constant.
No description provided.
The text was updated successfully, but these errors were encountered: