bitwalker / bitwalker/timex

Timex.shift yields incorrect results for leap year after update

Open
#709 1 comment 2 reactions 0 assignees View on GitHub
Dominant language
Elixir
Stars
1.8k
Forks
407
PR merge metrics
No merged PRs in 30d

Description

### Steps to reproduce

- API function called - Timex.shift
- Arguments provided - `Timex.shift(~D[2020-02-29], years: 1)`

### Description of issue

- The same arguments on version 3.6.1 yields the correct result of `~D[2021-02-28]` whereas the latest version 3.7.6 yields `~D[2021-03-01]`
-
image

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.