Commit Graph

15 Commits

Author SHA1 Message Date
lilleman 8e8fa92e77 Answer architecture round 1: Main draws the CLI's default seed and passes it to run, New names every option mistake at once, dataGiven says what it is, and the docs drop seeded where every sequence is 2026-10-12 18:34:15 +02:00
lilleman 7c0fa4075f Test that New names a nil module beside the missing seed, and that the CLI without --seed draws from the seed Main gives run 2026-10-12 18:34:15 +02:00
lilleman 90c804f6e6 Fail New without WithSeed, naming it, and seed the CLI from the system without --seed 2026-10-12 18:34:15 +02:00
lilleman 3ae8b9f1b1 Test that New without WithSeed fails naming it, that the CLI without --seed draws afresh each run, and seed every test's New 2026-10-12 18:34:15 +02:00
lilleman 71b0754679 Answer prose round 1: the custom-CLI test advice says why an indexed module needs each path rendered, the help ruling says the help points to --list and who ruled, ErrNoColumns's doc says what it matches, and the filed items read in one pass 2026-10-11 23:39:14 +02:00
lilleman 5e6330c75b Answer product-owner round 1: the hint for an empty stdin points to --list, the help's examples are templates only, the README's record id is an integer, and a test over an indexed module renders each path 2026-10-11 23:39:14 +02:00
lilleman 00257e2851 Test that the hint for an empty stdin points to --list 2026-10-11 23:39:14 +02:00
lilleman 9671600fff Give the help examples that read no data and the exit codes, say a data path is no directory in one shape, suggest a record of one for a choice, name a JSON syntax error's line and column, and say no data is loaded from FakeStruct 2026-10-11 23:39:14 +02:00
lilleman 1a7656d076 Test that the help's examples read no data and list the exit codes, a data path that is no directory says so in one shape, a choice suggests a record of one, a JSON syntax error names its line and column, and FakeStruct says no data is loaded 2026-10-11 23:39:14 +02:00
lilleman adba2510db Answer prose round 1: the CLI decision says what keeping cli off internal/ buys, the changelog and Library sentences hold one idea each, and item 185 names the three wordings its builder rules on 2026-10-11 21:19:57 +02:00
lilleman 81c7ff6737 Name each line of a joined error under the command, test the command name as a pure function, and pin the version line's fallback 2026-10-11 21:19:57 +02:00
lilleman 5b2bb7e681 Answer architecture round 2: every error a custom CLI prints names it, the help marks where the name goes, the version line checks the main module first, and the README embed compiles for data without a table 2026-10-11 21:19:57 +02:00
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
lilleman 35f1eeffb2 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
lilleman 35487cd36d Test the CLI as package cli's Main over the modules it is given, and fejkdata's main over the shipped packages 2026-10-11 21:19:57 +02:00