Skip to content

Conversation

@mbostock
Copy link
Member

Alternative to #985.

I snuck the axes state into the existing context argument rather than adding yet another positional argument to mark.render. This allows the mark to access the axis.ticks option (whose default value is populated automatically by Plot). I could probably sneak this state somewhere else if you prefer, say in dimensions?

I chose to make this a decoration mark (with no data), but in theory we could make this a mark with automatic data based on the tick values, which would allow variable color, stroke-width, and everything else… which could be cool.

Also, maybe we could find a way to remove the grid functionality from the current axis, and instead have the existing scale.grid option translate into an implicit Plot.gridX or Plot.gridY mark being added?

@mbostock
Copy link
Member Author

Superseded by #1197.

@mbostock mbostock closed this Dec 30, 2022
@mbostock mbostock deleted the mbostock/grid branch December 30, 2022 23:13
@mbostock mbostock mentioned this pull request Dec 31, 2022
36 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants