Skip to content

Record the template-literal backtick trap - #94

Merged
pseudoseed merged 1 commit into
mainfrom
docs/lesson-template-literal-backticks
Aug 24, 2026
Merged

Record the template-literal backtick trap#94
pseudoseed merged 1 commit into
mainfrom
docs/lesson-template-literal-backticks

Conversation

@pseudoseed

Copy link
Copy Markdown
Owner

Third occurrence in this repo — phase-stop-guard.ts once, db/schema.ts twice — each time while adding a well-intentioned explanatory comment.

db/schema.ts holds the entire SQL schema in one template literal, and SQL comments are the natural place to write prose about columns. So this:

-- `reason` collapses every not-clean gate verdict to 'busy', and the two that

terminates the string mid-schema and reports TS1005: ',' expected 200 lines further down, on code nobody touched.

Cold tier. It is a recognition cue for one file shape, not something that should change a decision up front, and the hot cap is load-bearing.

🤖 Generated with Claude Code

Third occurrence in this repo -- phase-stop-guard.ts once, schema.ts twice --
each time while adding an explanatory comment inside a big template literal.
db/schema.ts holds the entire SQL schema in one, and SQL comments are the
natural place to write prose about columns, so a backticked identifier
terminates the string mid-schema and reports TS1005 on a line 200 further down.

Cold tier: it is a recognition cue for one file shape, not something that should
change a decision up front, and the hot cap is load-bearing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@pseudoseed
pseudoseed merged commit d3c9d90 into main Aug 24, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant