ingitdb / dalgo2ingitdb4github / 33022418963

85%

push

github

fix: bump dalgo to v0.74.0, record to v0.1.3; close duplicate-insert conformance gap (#5)

dal.DB's sealing (the unexported dalgoDB() marker method) has not changed
shape since this adapter adopted it for v0.64.2; the interface is satisfied
unchanged at v0.74.0 with no adapter redesign required.

dal-go/record v0.1.3 added the cross-adapter ErrRecordExists / IsAlreadyExists
sentinel that dalgo's dalgotest.Checks() conformance suite now mandates
("rejects an Insert over an existing key with record.IsAlreadyExists").
Insert's existing-key error in tx_readwrite.go now wraps
record.ErrRecordExists in both the MapOfRecords and single-record branches,
so callers can distinguish "created" from "duplicate key" via
record.IsAlreadyExists(err) instead of string-matching an ad hoc message.

Fixture fix: newGitHubContentsServer's GET handler 404'd any path not present
in the server's static fixture set, even after that path had been written via
PUT during the test. That masked the new conformance check: a record written
by a seed Insert always read back as "not found" on the next Insert, so
duplicate-key detection looked broken. Directory listings still come from the
static fixtures; file content now comes from the live contents map for any
path, matching what the real GitHub Contents API does.

go.mod's `go` directive moved from 1.26.0+toolchain 1.27.0 to a plain 1.27.0
as a mechanical side effect of `go get`/`go mod tidy` against dalgo v0.74.0's
own go.mod floor.

go build ./... && go vet ./... && go test ./... all green.


Claude-Session: https://claude.ai/code/session_01KFsyYhYi9h9Am1JbAMxuhv

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

2 of 2 new or added lines in 1 file covered. (100.0%)

1195 of 1413 relevant lines covered (84.57%)

0.85 hits per line