`axisBottom.tickValues` does not respect string interval when crossing end of month boundaries

Describe/explain the bug I’m running into a strange issue with using intervals in tickValues (every 3 days, every 7 days, etc). When the data moves past the end of the month, the tickValue interval is thrown off. As you can see in the screenshot, both 07/31 and 08/1 ticks are shown next to each other and does not hold up to the every 3 days interval.

To Reproduce

1. Use a line chart that uses a time series for the X Axis
2. Use a dataset that crosses over the end of a month (i.e. 07-29-2020 through 08-08-2020)
3. Use a tickValues interval of “every 3 days”, “every 7 days”, etc

Reproduced in this code sandbox: https://codesandbox.io/s/brave-brown-9qd33

Expected behavior I would expect the X-Axis to understand the end of the month and continue its interval of three days (or whatever the interval is). In my example, the X-Axis would look like this:

To get around this for now, I was able to manually assign x-axis tick values: https://codesandbox.io/s/cocky-firefly-tekbg I’ll likely just create these tick values based on my data set and then format my dates via a function in axisBottom.format.

Desktop (please complete the following information):

• OS: MacOS Catalina 10.15.6
• Browser: Chrome
• Version: 84.0

[fillippeyton]

Looks like an issue based on the usage of d3.ticks with d3.timeDay.every(n)

http://jsfiddle.net/myqhpogs/

var x = d3.scaleTime()
    .domain([new Date('2020-08-28'), new Date('2020-09-13')]);

console.log(x.ticks(d3.timeDay.every(5)));

// result
[
  0: Mon Aug 31 2020 00:00:00 GMT-0700 (Pacific Daylight Time) {},
  1: Tue Sep 01 2020 00:00:00 GMT-0700 (Pacific Daylight Time) {},
  2: Sun Sep 06 2020 00:00:00 GMT-0700 (Pacific Daylight Time) {},
  3: Fri Sep 11 2020 00:00:00 GMT-0700 (Pacific Daylight Time) {},
]

[fillippeyton]

bump

On Sun, Mar 28, 2021 at 2:48 PM stale[bot] @.***> wrote:

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, “bump”), and we’ll keep it open. We are sorry that we haven’t been able to prioritize it yet. If you have any new additional information, please include it with your comment!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/plouc/nivo/issues/1101#issuecomment-808964586, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7P52PXKYIO2HCFIXF7NE3TF6P3HANCNFSM4P7TOPRQ .