Skip to content

chore: replace em dashes in source and output strings (#1283) - #1285

Open
prx-my wants to merge 2 commits into
OWASP:mainfrom
prx-my:chore/issue-1283-em-dashes
Open

prx-my wants to merge 2 commits into
OWASP:mainfrom
prx-my:chore/issue-1283-em-dashes

Conversation

@prx-my

@prx-my prx-my commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

Closes #1283.

What changed

  • Replaced all 54 em dashes across 17 files under src/ (43 in emitted strings, 11 in comments/JSDoc):
    • Emitted clauses use : where a clause follows (e.g. 1 packument fetch failed: remediation guidance may be incomplete.), ;/period where a colon read poorly
    • HTML <title> separators use - (CVE Lite - <project>)
    • Comments and JSDoc use a plain -
  • Updated the 8 tests that assert these strings exactly (multi-folder-scan, scanner-cache, html-reporter) after reading each assertion
  • Also cleaned repo docs: README.md (10), docs/output-before-after.md (8), scripts/clean-dist.mjs (1). The docs/ sample output now matches current source (printers.ts colon, formatters.ts hyphens)
  • Verified src/skills/content.ts output by eye (shipped AI-assistant docs, least coverage)

Verification

  • grep -rn "—" src --include="*.ts" returns nothing
  • npm test passes (163 suites, 2249 tests)
  • npm run build is clean

Notes

  • tests/output.test.ts:2944 intentionally keeps not.toContain("—") as the convention guard.
  • Out of scope for this PR: website/docs/ (859) and examples/ (68) still contain em dashes; can be a follow-up docs PR.

Copilot AI balanced review requested due to automatic review settings October 3, 2026 20:24
@prx-my
prx-my requested a review from sonukapoor as a code owner October 3, 2026 20:24

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@prx-my

prx-my commented Oct 7, 2026

Copy link
Copy Markdown
Contributor Author

Update: this branch has been refreshed with the latest main. It is no longer behind and now only awaits the required review/status checks before it can merge.

@prx-my
prx-my force-pushed the chore/issue-1283-em-dashes branch from 4d8e5cf to c64488b Compare October 8, 2026 11:47
Replace all 54 em dashes across 17 files under src/ with colons, hyphens, or periods, and update the tests that assert those strings. Also clean README.md, docs/output-before-after.md, and scripts/clean-dist.mjs. Comments and JSDoc use a plain hyphen.
@prx-my
prx-my force-pushed the chore/issue-1283-em-dashes branch from c64488b to 47de9ac Compare October 8, 2026 11:50

This branch has not been deployed

No deployments
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.

chore: replace the em dashes in shipped source and output strings

2 participants