eric/ConfigKit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Cover integer version decoding boundaries

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-12 00:28:35 +00:00
parent f5bbc2be5d
commit 6eb40c5492
2 changed files with 226 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/roadmap/implementation.md
View File

@@ -58,7 +58,7 @@ the scalar, destination-type, and semantic-path boundary matrix.
## Stage 2 — Close scalar and path-boundary gaps
Status: not started. Depends on: Stage 1.
Status: complete (2026-09-12). Depends on: Stage 1.
Scope: focused tests in `load_test.go`, `decode_test.go`, and relevant path/decoder
helpers only where those tests expose defects. Avoid broad schema refactoring.
@@ -82,6 +82,14 @@ loads. Expand a stage-1 test instead of duplicating the same behavior.
Validation: `go test . -run 'Version|Decode|Path'`, then the everyday checker.
Completion record: boundary coverage now includes exact zero, negative, negative
zero, unbounded textual integer, rejected scalar/container kinds, parsed numeric
tokens in maps and sequences, escaped keys, named and nested-pointer strings, and
ordinary numeric, dynamic, codec, duration, and secret destinations. Existing
parser-policy tests continue to own non-JSON number rejection. The focused command
and `./scripts/check.sh` pass with Go 1.26.7 on Linux. Stage 3 should verify retained
history, rendering, composition ownership, detachment, and redaction invariants.
## Stage 3 — Verify provenance and pipeline invariants
Status: not started. Depends on: Stage 2.