jschoubben
71a35a6376
The delivery repository's contracts and SDK live under modules/ as mesh-delivery-contracts and mesh-delivery-sdk, their Go module paths renamed to match the folders (the TypeScript names already did), and every importer in mesh-delivery, mesh-catalog, mesh-host, mesh-tools and mesh-sdk follows in the same group: a design as it should be, one path per module, checked by the group's check building every importer. Builds: design 47 G §427, §88 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
16 lines
920 B
Go
16 lines
920 B
Go
package buildstep
|
|
|
|
// ModuleTree is what a merge holds of one module directory, as a build module's preview answers it (novox/hq ADR 0484
|
|
// clause 3, as ADR 0593 §2 changes it): its git tree id, the sha256 of its module.json, the sha256 of each lock file it
|
|
// has (go.sum, package-lock.json), and, of a module whose every artifact names its paths, each named path's git object
|
|
// id at the commit. The indexer alone computes from them (the named tree, the fingerprint); the build module's runner
|
|
// (mesh-build-go's buildstep.ModuleTrees) fills them.
|
|
type ModuleTree struct {
|
|
Tree string `json:"tree"`
|
|
Manifest string `json:"manifest"`
|
|
Locks map[string]string `json:"locks,omitempty"`
|
|
Paths map[string]string `json:"paths,omitempty"`
|
|
// Packages are no longer filled (ADR 0593 §2): kept so a preview written before still decodes.
|
|
Packages []string `json:"packages,omitempty"`
|
|
}
|