feat: implement date segment type for part number generation #79

New Issue

forbes · 2026-02-13T19:03:25Z

forbes commented

2026-02-13 19:03:25 +00:00

Ref: docs/ROADMAP.md § Appendix B / 1.5 Missing Segment Types

The schema parser accepts type: "date" segments but the generator returns an error:

// internal/partnum/generator.go, resolveSegment()
case "date":
    // TODO: implement date formatting
    return "", fmt.Errorf("date segments not yet implemented")

Tasks:

Implement date formatting in resolveSegment() with strftime-style format support
Support common patterns: YYYYMMDD, YYYY-MM-DD, YY, YYMM, etc.
Use the segment's format field from the schema YAML to control output format
Handle timezone (default to UTC)
Add tests in internal/partnum/generator_test.go for date segments

Files:

internal/partnum/generator.go — implement the "date" case
internal/schema/schema.go — verify date type validation accepts format field
internal/partnum/generator_test.go — add test cases

**Ref:** `docs/ROADMAP.md` § Appendix B / 1.5 Missing Segment Types The schema parser accepts `type: "date"` segments but the generator returns an error: ```go // internal/partnum/generator.go, resolveSegment() case "date": // TODO: implement date formatting return "", fmt.Errorf("date segments not yet implemented") ``` **Tasks:** - [ ] Implement date formatting in `resolveSegment()` with strftime-style format support - [ ] Support common patterns: `YYYYMMDD`, `YYYY-MM-DD`, `YY`, `YYMM`, etc. - [ ] Use the segment's `format` field from the schema YAML to control output format - [ ] Handle timezone (default to UTC) - [ ] Add tests in `internal/partnum/generator_test.go` for date segments **Files:** - `internal/partnum/generator.go` — implement the `"date"` case - `internal/schema/schema.go` — verify date type validation accepts format field - `internal/partnum/generator_test.go` — add test cases

forbes referenced this issue from a commit

2026-02-13 19:11:02 +00:00

feat: implement date segment type for part number generation

forbes referenced a pull request that will close this issue

2026-02-13 19:11:12 +00:00

fix: style guide compliance batch 1 + date segment type #83

forbes closed this issue

2026-02-13 19:13:36 +00:00

forbes referenced this issue from a commit

2026-02-14 14:54:22 +00:00

docs: update roadmap status for completed Tier 0 items

Sign in to join this conversation.