Generally, I did see several requests to change the strategy when
calculating next month/year. However, that would be a breaking change.
I'd only go for it if people are strongly in favor of the change.
So, changing this to a poll.
When Temporal encounters inputs representing a month and/or day that
doesn't exist in the desired calendar year, by default (overridable in
with or from via the overflow option) the inputs will be adjusted using
the following algorithm:
- First, pick the closest day in the same month. If there are two
equally-close dates in that month, pick the later one.
- If the month is a leap month that doesn't exist in the desired year,
then pick another date according to the cultural conventions of that
calendar's users. Usually this will result in the same day in the month
before or the month after where that month would normally fall in a leap
year.
- Otherwise, pick the closest date to the provided date that is still in
the same year. If there are two equally-close dates, pick the later one.
- If the entire year doesn't exist, then pick the closest date to the
provided date. If there are two equally-close dates, pick the later one.