Skip to content

Add-a-type checklist in docs/ #50

Closed as not planned
Closed as not planned

Description

@CaffeinatedCoder

Adding a range type or a value set family touches the type, its factory, the JSON and TypeConverter attributes, AOT converter registration, the EF registry, the NodaTime satellite if it applies, the changelogs and the docs. Most of it is enforced by convention tests, but you only find out what you forgot when one fails.

Write it down as one checklist in docs/, with each step naming the test that would catch it if you skipped it.

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. Docs, tests and internal work aren't tied to a version, so this doesn't need a milestone until someone picks it up.

    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. CaffeinatedCoder commented on Oct 18, 2026

    @CaffeinatedCoder
    OwnerAuthor

    Superseded by #174 (PR #176), which documents the add-a-type procedure in docs/architecture.md#adding-a-range-or-set-type, built on the clone sweep rather than a checklist.

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

    documentationImprovements or additions to documentationduplicateThis issue or pull request already exists

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions