lilleman 9528ecd8b0 Answer architecture round 1: a custom CLI names itself by its file, --version names its module beside fejkdata's and follows a replace, the module path comes from the library's type, the end-to-end test runs main in a subprocess, the CLI tests find the shipped modules by their manifests, and Your own CLI sits under Library

2026-10-11 21:19:57 +02:00

..

main_test.go

Answer architecture round 1: a custom CLI names itself by its file, --version names its module beside fejkdata's and follows a replace, the module path comes from the library's type, the end-to-end test runs main in a subprocess, the CLI tests find the shipped modules by their manifests, and Your own CLI sits under Library

2026-10-11 21:19:57 +02:00

main.go

Make the CLI the library call cli.Main, with fejkdata's own main one line over data.Modules()

2026-10-11 21:19:57 +02:00