Skip to content

fix(scripts): escape blocked link report cells - #970

Open
Aurantium-47 wants to merge 1 commit into
practical-tutorials:masterfrom
Aurantium-47:codex/escape-blocked-link-report-cells
Open

Aurantium-47 wants to merge 1 commit into
practical-tutorials:masterfrom
Aurantium-47:codex/escape-blocked-link-report-cells

Conversation

@Aurantium-47

Copy link
Copy Markdown

What is this?

Tooling-only fix for the weekly link-rot report. Blocked/unverifiable rows currently bypass the cell escaping used by the other report sections, so pipes in a tutorial title or fetched note create extra columns and @ text can be interpreted as a mention.

Pass the four cells through the existing escape_md_cell helper, using the same formatting style as the moved-links table.

Validation

  • Local HTTP flow: HEAD 405, GET 200 with a soft-404 title, domain-policy classification as BLOCKED, then report generation. Pipe and mention controls fail on the original and pass after the fix.
  • Ordinary dead, suspect, moved, and blocked reports remain byte-for-byte identical; empty blocked cells retain their existing display.
  • python3 scripts/check_readme.py lint --json: exit 0, 457 entries, 0 errors and 0 warnings.
  • Python syntax compilation passed on Windows with Python 3.12.

Checklist

  • This is a tooling-only change.
  • I ran the README validator locally and it exits 0.
  • Tutorial URL, section placement, and author relationship checks are not applicable to this tooling change.

AI assistance: Codex investigated, implemented, and validated this tooling fix.

Use the existing Markdown cell helper for blocked entries, matching the other report sections.

Assisted-by: OpenAI Codex <noreply@openai.com>
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