datatug / datatug-core / 35312691322

91%

push

github

feat(storage): author static inGitDB project schema (#335)

Source commits:

- 241dadddbb4c feat(storage): author static inGitDB project schema
  Author DataTug's inGitDB project-store schema as static files in inGitDB's
  existing on-disk format: .ingitdb/root-collections.yaml registers ext, and
  one .collection/definition.yaml per project-item collection under it
  (projects, then queries, entities, environments/servers/catalogs, dbmodels,
  boards, recordsets, folders, dbdrivers/dbservers, credentials). Each
  collection's record_file carries name: '{key}/{key}.<suffix>.json',
  format: json, type: map[string]any and a nested records_dir: '.', per the
  Feature's suffix table.
  The schema is embedded in datatug-core via embed.FS and copied into a store
  directory by the new WriteSchema(dir) function, which refuses to overwrite
  a differing existing file and is idempotent when content already matches.
  No dalgo or dalgo2ingitdb import: this package only copies bytes it never
  parses (founder, 2026-09-17: "DataTug project ingitdb schema should be
  defined and copy-pasted... if we need modify ingitdb schema it belong to
  ingitdb module, not dalgo").
  Tests prove the AC directly: the queries definition carries the four
  record_file keys with records_dir nested (not a sibling); every collection
  and subcollection in the tree loads through ingitdb-go v0.6.1's strict
  KnownFields(true) reader (validator.ReadDefinition); and a copy with
  records_dir moved to a sibling key is rejected as an unknown field.
  The round-trip through dalgo2ingitdb.NewDatabase (writing query q1 for
  project p1 and asserting it lands at
  ext/datatug/projects/p1/queries/q1/q1.query.json) is deliberately not in
  this package: dalgo2ingitdb is a DALgo driver, and datatug-core's go.mod
  must not carry one (REQ:project-store-is-a-dalgo-database), even as a test
  dependency. That integration test is added separately in datatug-cli,
  which already depends on the drive... (continued)

59 of 78 new or added lines in 3 files covered. (75.64%)

9793 of 10827 relevant lines covered (90.45%)

0.91 hits per line