You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 19, 2023. It is now read-only.
Should separate the cmd prompt rule into two rules
One rule check valid command prompts
New rule checks that example content is prepended with .Example output
Tricky bit is that some file contents are displayed using the terminal attribute. I think file contents shouldn't use the terminal attribute, possibly just [source]. If they do use the terminal attribute, it may incorrectly flag the cmd prompt rule.
The text was updated successfully, but these errors were encountered:
The cmd prompt rule needs to be aware if there's an Example output heading before the code block.
The Example output rule needs to be aware if there's no cmd prompt at the start of the line in a code block.
So you essentially have the same regex for both rules, just different error messages. Because it's the same regex, the rules trigger in the exact same place, which isn't ideal. And it's usually either one problem or the other, not both.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Following on from #2 .
Should separate the cmd prompt rule into two rules
.Example output
Tricky bit is that some file contents are displayed using the terminal attribute. I think file contents shouldn't use the terminal attribute, possibly just [source]. If they do use the terminal attribute, it may incorrectly flag the cmd prompt rule.
The text was updated successfully, but these errors were encountered: