Skip to content

Calendar factories for DateRange (month, quarter, year, week) #48

Closed

Description

@CaffeinatedCoder

Factories for the calendar ranges people build by hand most often: a month, a quarter, a year, an ISO week.

// names are a sketch
DateRange.Month(2026, 10);   // [2026-10-01,2026-11-01)
DateRange.Quarter(2026, 4);  // [2026-10-01,2027-01-01)

Deferred from 9.0.0. The names and the week rule (ISO 8601, or the current culture's first day of week) are hard to change later, so settle them before shipping. NodaTime's LocalDateRange and YearMonthRange probably want the same set.

Activity

  1. added this to the 9.1.0 milestone on Oct 17, 2026
  2. removed this from the 9.1.0 milestone on Oct 17, 2026
  3. CaffeinatedCoder commented on Oct 17, 2026

    @CaffeinatedCoder
    OwnerAuthor

    Moved off 9.1.0 into the backlog (#83), with no milestone.

    release/9.x has been cut, and 9.1.0 ships with the work that's already finished. Nothing has started on this issue, and it shouldn't hold up the tag. This is an addition, so the 10.0.0 epic (#58) doesn't take it either: that epic is kept to the silent and breaking fixes so they aren't held up behind new features.

    When someone picks it up, it goes under the epic of the release it will ship in and takes that milestone. A 9.x minor would need the change cherry-picked onto release/9.x.

  4. added this to the 10.0.0 milestone on Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/rangesRange unions, variants and the shape enginesenhancementNew feature or requestpackage/coreAffects CodoMetis.ValueRangespackage/nodatimeAffects CodoMetis.ValueRanges.NodaTime

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions