compose/internal/projectloader
Nicolas De Loof 6698708752 refactor(projectloader): move project loading and generation to internal/projectloader
LoadProject and Generate (the api.ProjectLoader operations) need two things
from the engine: the Docker API, to read the containers a project is
generated from, and the Docker CLI, which resolves remote Compose files.

They now live in internal/projectloader, along with the unsupported
attributes detection only the loader uses, behind a Backend interface that
composeService implements in a new file of pkg/compose, like internal/inspect.
The tests move with the code; their assertions are unchanged, only the way
the service is built differs.

The canonical container name, which both this package and internal/inspect
need, moves to a tiny internal/naming package instead of being copied a
third time. pkg/compose keeps its own copy until the shared kernel is
extracted.

Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
2026-10-13 10:03:53 +02:00
..
generate.go refactor(projectloader): move project loading and generation to internal/projectloader 2026-10-13 10:03:53 +02:00
loader.go refactor(projectloader): move project loading and generation to internal/projectloader 2026-10-13 10:03:53 +02:00
loader_test.go refactor(projectloader): move project loading and generation to internal/projectloader 2026-10-13 10:03:53 +02:00
projectloader.go refactor(projectloader): move project loading and generation to internal/projectloader 2026-10-13 10:03:53 +02:00
unsupported_attributes.go refactor(projectloader): move project loading and generation to internal/projectloader 2026-10-13 10:03:53 +02:00
unsupported_attributes_test.go refactor(projectloader): move project loading and generation to internal/projectloader 2026-10-13 10:03:53 +02:00