Skip to content

fix: skip fenced code blocks in body/posix-paths - #356

Open
MaximeGaudin wants to merge 2 commits into
mainfrom
fix/issue-97-posix-paths-fences
Open

fix: skip fenced code blocks in body/posix-paths#356
MaximeGaudin wants to merge 2 commits into
mainfrom
fix/issue-97-posix-paths-fences

Conversation

@MaximeGaudin

Copy link
Copy Markdown
Owner

Summary

  • body/posix-paths scanned every body line, so a Windows-style path inside a fenced example (e.g. a "Before:" line in a ```text block) was flagged as a real path, while body/imperative-instructions in the same file already tracks fences.
  • The rule now skips lines inside fenced code blocks, using the same fence tracking the imperative rule uses.

Fixes #97

Test plan

  • New regression test failed before the fix
  • New regression test passes after the fix
  • Local checks mirror CI and passed before push
  • CI green on the PR

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.

body/posix-paths fires inside fenced code blocks, unlike every other body rule

1 participant