Skip to content

[fix] doccov: handle fenced code blocks (post-fence table backticks)#9

Merged
vt128 merged 1 commit into
masterfrom
fix/doccov-fenced-blocks
Jun 15, 2026
Merged

[fix] doccov: handle fenced code blocks (post-fence table backticks)#9
vt128 merged 1 commit into
masterfrom
fix/doccov-fenced-blocks

Conversation

@vt128

@vt128 vt128 commented Jun 15, 2026

Copy link
Copy Markdown
Member

backtickWords mis-paired inline spans across fenced blocks, so a backtick reference in a markdown table after a fenced example was missed — the doc-split hit this (config accessors in a Configuration table read as undocumented, needing a redundant fenced-list workaround). Fix: extract+strip fenced blocks first, then match inline spans on the remainder. Regression test added; go test -race ./doccov/ green. Lets the standard Configuration table satisfy doccov -config directly.

🤖 Generated with Claude Code

… count

backtickWords mis-paired single-backtick spans across ```fenced``` blocks, so a
`code` reference in a markdown table that follows a fenced example could be
missed (surfaced in the doc-split: config accessors documented only in a
Configuration table read as undocumented, forcing a redundant fenced-list
workaround). Now fenced blocks are word-extracted and stripped first, then
inline spans are matched on the clean remainder. Regression test added.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vt128 vt128 merged commit cc6a3ec into master Jun 15, 2026
10 checks passed
@vt128 vt128 deleted the fix/doccov-fenced-blocks branch June 15, 2026 15:21
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