ingitdb / dalgo2ingitdb

100%

push

github

fix: discover logical inGitDB root collections consistently (#24)

Native schema discovery currently returns physical directory paths that the driver's query and keyed-read APIs do not recognize when `.ingitdb/root-collections.yaml` maps logical IDs to other paths. For example, `baseline: collections/baseline` is queried as `baseline` but discovered as `collections/baseline`, while describing `baseline` attempts the wrong schema path.

Use the configured definition reader for schema discovery and description. List sorted logical root IDs; map the fully resolved collection definition directly so inherited columns, shared-directory layouts and `data_dir` retain the reader's semantics. Existing source-schema, indexes, constraints, field types and default-value conversion remain covered.

Compatibility: SchemaReader now treats the reader's logical root IDs as authoritative, matching existing transactions. It no longer discovers unregistered physical directories or accepts their paths as root identities. Missing/invalid mappings follow the configured reader's behavior, without a physical-path fallback. ListCollections continues to ignore its parent argument; scoped DescribeCollection uses the existing scoped resolver, without introducing scoped enumeration.

Regression coverage uses the original three-root native Shipping JSONL fixture with its unchanged map and records, checking exact discovered IDs and describe/query/keyed reads for every discovered root. Additional cases cover alias/custom nested physical paths, identity mapping, unregistered/unknown IDs, missing/invalid mappings, inherited schemas with a separate data directory, and scoped descriptions.

Validation: exact committed driver candidate passes `go test ./...` (56.921s). Focused regressions also pass and include schema API calls inside a write transaction. Independent adversarial review r1 passed with no remaining findings at the exact candidate. Publication/release and downstream Cloud depe... (continued)

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

4898 of 4898 relevant lines covered (100.0%)

1.01 hits per line