Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add utcMonthDay, timeMonthDay #63

Closed
wants to merge 2 commits into from
Closed

add utcMonthDay, timeMonthDay #63

wants to merge 2 commits into from

Conversation

mbostock
Copy link
Member

Fixes #62.

I think it’s proven pretty surprising that d3.utcDay.every(3) is not regularly spaced, so better to match d3.utcDay behave the way people expect, and have d3.utcMonthDay for the month-aligned day interval. Same goes for d3.timeDay, and now we don’t need the awkwardly named d3.unixDay (though I’ll keep it as a deprecated alias for backwards compatibility).

@mbostock mbostock requested a review from Fil June 25, 2023 21:01
@mbostock
Copy link
Member Author

We also need to delete the README here and point to the new documentation on d3js.org, and update the documentation there… I’ll do that separately.

@mbostock
Copy link
Member Author

Broader discussion in #64, wherein I think we should consider changing the behavior of interval.every universally. The main wrinkle is d3.timeHour and daylight savings time… Also, arguably, the design of D3’s “multi-scale” tick format, but I think that becomes less important now that we have a better strategy for time axes in Observable Plot.

@mbostock
Copy link
Member Author

mbostock commented Jun 3, 2024

Closing in favor of #66.

@mbostock mbostock closed this Jun 3, 2024
@mbostock mbostock deleted the mbostock/month-day branch June 3, 2024 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Equivalent of d3.unixDay for local time
2 participants