datatug / datatug-core / 35318100002

91%

push

github

feat(storage): implement storage.Store for the DALgo project store (#336)

Task 5 (part 2) of the dalgo-project-store plan: `dalgostore.Store` implements `storage.Store` over the caller-supplied `dal.DB` that part 1 already uses for a single project. Later commits apply the review round and the founder's title ruling to filestore as well.

Source commits:

- a6fffaec1800 feat(storage): implement storage.Store for the DALgo project store
  Task 5 (part 2) of the dalgo-project-store plan. dalgostore.Store now
  implements storage.Store over the caller-supplied dal.DB part 1 already
  uses for a single project:
  - GetProjectStore returns part 1's ProjectStore, without checking that the
  project exists (as filestore does).
  - CreateProject validates the request, derives a readable project id from
  the title, installs the static inGitDB schema with
  ingitdbschema.WriteSchema and inserts the project record at
  ext/datatug/projects/<id>. Insert, not Set, so a taken id fails with
  record.ErrRecordExists instead of overwriting.
  - DeleteProject deletes that record (idempotent, matching DALgo's Deleter).
  - GetProjects lists ext/datatug/projects and returns a brief per record.
  dal.DB exposes no filesystem path, so the inGitDB store root WriteSchema
  needs is supplied to NewStore by whoever constructs the db, exactly as
  filestore's own NewStore is handed its projects' paths. No library is
  changed and no new exported interface is introduced; deps_test.go still
  proves no DALgo driver is imported.
  pkg/storage/dalgostore is at 100% statement coverage.
- 9e36e634c5c1 fix(storage): caller-supplied project id, title in the record, no schema install
  Review round on #336:
  - dto.CreateProjectRequest gains a required `id`, validated by a new
  project-id rule (1-64 chars, lower-case ASCII letters, digits, "-" and
  "_", first and last a letter or digit). CreateProject uses it as the key
  and the slug derivation is gone. Breaking: every create_proje... (continued)

102 of 102 new or added lines in 5 files covered. (100.0%)

9893 of 10927 relevant lines covered (90.54%)

0.91 hits per line