fix: add template variable syntax guidance - #14
Merged
Conversation
Template variables require Go text/template double-brace syntax
({{.varname}}) and alphabetic names. Without this guidance, users
create templates with invalid syntax like {.0} that passes through
as literal text instead of being substituted.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
chris-regnier
force-pushed
the
fix/template-variable-syntax
branch
from
February 16, 2026 17:33
552f523 to
d4a5d49
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
diaryctl template createdocumenting that template variables use Go{{.varname}}syntax and must start with a letter{{.first}}/{{.second}}/{{.third}}instead of invalid{.0}/{.1}/{.2}syntax (done via CLI, not in code)Context
The
template.Render()function uses Go'stext/template, which requires double-brace{{.varname}}syntax. Additionally, numeric keys like.0are interpreted as integer literals by Go templates, not map key lookups — so{{.0}}silently outputs0instead of the variable value.Test plan
go test ./internal/template/...— no regressionsgo test ./cmd/...— no regressionscreate_entrywithtemplate_names: ["three-things"]andtemplate_variables: {"first": "a", "second": "b", "third": "c"}— variables substituted correctly🤖 Generated with Claude Code