turbo-editors/turbo-go · 2026-09-01-tool-parameters.md

⑂ main

2026-09-01-tool-parameters.md · 33 lines · 1.8 KBmarkdown    Blame HistoryRaw
   1# Handoff — 2026-09-01 — Tool parameters
5The feature itself is turbo-core's; see its handoff of the same date. What changed here is small and green:
7- the starter tools file now teaches `{{label}}` and `{{label...}}` in its comments;
8- one installer test that asserted before checking it was in a git checkout.
10Whole suite green, quality gate PASS at 0/0/0.
12**Committed and released as v0.2.2** at `d64410c`, which is exactly HEAD. Working tree clean, on `main`. The dependency is the published `turbo-core v0.1.0`, with no active `replace`.
14## In flight
18## Next steps
201. **Try a parameterised tool in real work.** Nobody has, and the first hour of it will find something.
212. **Two lines of tidying in `go.mod`**, whenever something else takes you there: the commented-out replace block, whose text is now false, and the missing trailing newline.
23## Open questions / blockers
27## Watch out for
29- **turbo-core v0.1.0 does not contain its own `02-release.publish.sh`.** That library's tag was cut one commit early. It changes nothing here, but do not be surprised by the gap when reading its release page.
31- **The placeholder examples are in comments, not tools.** `TestTheCreatedToolsFileStillLoadsWithItsPlaceholderExamples` exists because the loader reads the whole file: if one of those examples ever became a real `[[tool]]`, `Create tools file` would start asking everybody for a value.
32- **No backticks in the templates.** They are raw Go strings, so a backtick ends the literal. The first draft of the comment block used them for `awk '{print $1}'` and would not compile; the prose says it without them.
33- **The installer test skips outside a git checkout**, because `unknown` is then the right answer. If you see it skipped in CI, check whether the checkout is shallow rather than assuming the test is broken.

📦 Turbo Go 3d7798b k33g 11h ago	1	# Handoff — 2026-09-01 — Tool parameters
	2
	3	## State
	4
	5	The feature itself is turbo-core's; see its handoff of the same date. What changed here is small and green:
	6
	7	- the starter tools file now teaches `{{label}}` and `{{label...}}` in its comments;
	8	- one installer test that asserted before checking it was in a git checkout.
	9
	10	Whole suite green, quality gate PASS at 0/0/0.
	11
	12	Committed and released as v0.2.2 at `d64410c`, which is exactly HEAD. Working tree clean, on `main`. The dependency is the published `turbo-core v0.1.0`, with no active `replace`.
	13
	14	## In flight
	15
	16	Nothing.
	17
	18	## Next steps
	19
	20	1. Try a parameterised tool in real work. Nobody has, and the first hour of it will find something.
	21	2. Two lines of tidying in `go.mod`, whenever something else takes you there: the commented-out replace block, whose text is now false, and the missing trailing newline.
	22
	23	## Open questions / blockers
	24
	25	None.
	26
	27	## Watch out for
	28
	29	- turbo-core v0.1.0 does not contain its own `02-release.publish.sh`. That library's tag was cut one commit early. It changes nothing here, but do not be surprised by the gap when reading its release page.
	30
	31	- The placeholder examples are in comments, not tools. `TestTheCreatedToolsFileStillLoadsWithItsPlaceholderExamples` exists because the loader reads the whole file: if one of those examples ever became a real `[[tool]]`, `Create tools file` would start asking everybody for a value.
	32	- No backticks in the templates. They are raw Go strings, so a backtick ends the literal. The first draft of the comment block used them for `awk '{print $1}'` and would not compile; the prose says it without them.
	33	- The installer test skips outside a git checkout, because `unknown` is then the right answer. If you see it skipped in CI, check whether the checkout is shallow rather than assuming the test is broken.