Future: error categorization in baseline validation (looks-like-typo, looks-like-encoding, ...) #28
Labels
No labels
area:ci
area:docs
area:engineering
area:framework-fp
area:test-coverage
dogfood:fn
dogfood:fp
dogfood:friction
dogfood:tp
phase:b
phase:c
severity:critical
severity:high
severity:low
severity:medium
source:deepseek-v4-pro
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/fallow-py#28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Future enhancement (operator suggestion, 2026-05-05)
ADR 0002 made baseline validation raise
ConfigErrorwith field-specific message. Operator suggested further UX improvement: categorize the error.Scope
_validate_baseline_shape()insrc/pyfallow/baseline.pycould pattern-match on the malformed value and return a category along with the error:looks-like-typo(fingerprint is a number that's close to a known fingerprint string when stringified)looks-like-encoding-issue(UTF-8 BOM in JSON, mojibake in fingerprint string)looks-like-merge-conflict(presence of<<<<<<<markers)looks-like-truncated(file ends mid-object)unknown-shape(default)Priority
Low. UX polish. Dogfood window will surface if this is real friction or just nice-to-have.
Phase
Phase C (Show HN polish). Open dogfood label
dogfood:frictionif encountered during the window.