Skip to content

fix: preserve escaped pipes in nexus page table cells#61

Merged
codepuncher merged 1 commit into
mainfrom
fix/nexus-page-escaped-pipes
Jun 20, 2026
Merged

fix: preserve escaped pipes in nexus page table cells#61
codepuncher merged 1 commit into
mainfrom
fix/nexus-page-escaped-pipes

Conversation

@codepuncher

Copy link
Copy Markdown
Owner

The Markdown pipe-table parser in scripts/generate-nexus-page.py split each row on every |, so a cell containing an escaped pipe (\|) was incorrectly fractured into multiple cells.

Split on unescaped pipes only (re.split(r"(?<!\\)\|", ...)) and unescape \|| within each cell.

Verified against a table containing escaped pipes; the real README still generates identical output.

Mirrors the same fix applied upstream in the CommonLibSSE-NG-template.

Copilot AI review requested due to automatic review settings June 20, 2026 17:51

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes the Nexus-page BBCode generator’s Markdown pipe-table parsing so escaped pipes (\|) inside table cells don’t incorrectly split the row into extra cells. This ensures tables in the README “nexus” block convert reliably to BBCode when cell content includes literal pipe characters.

Changes:

  • Update the table row splitting logic to split only on unescaped | characters using re.split(r"(?<!\\)\|", ...).
  • Unescape \| to | within each parsed cell before inline Markdown→BBCode conversion.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@codepuncher codepuncher merged commit 2327462 into main Jun 20, 2026
14 checks passed
@codepuncher codepuncher deleted the fix/nexus-page-escaped-pipes branch June 20, 2026 18:02
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.

2 participants