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
The changes implemented by this commit causes the problem to exist: f769fcd
// NOTE: If the `ctx` document is large (as could be the case with
// `scope: raw`) this is *slow*. Thus, the cap at 1k.
//
// TODO: Actually fix this.
I have a rule that looks for incorrectly indented content. It uses the following token:
extends: existence
message: 'Content must be indented using 4x spaces each time. "%s"'
level: error
nonword: true
scope: raw
tokens:
- '^[ ]{1,3}\`'
When the Markdown file contains 999 characters or more (i.e. ctx > 1000), the ^ part of the token stops using the start of the line properly and invents (hallucinates) new starting positions.
Attached are sample files that exactly show the spillover in the logic: vale.zip
Consequently, text with four spaces before the first ` is flagged as incorrect, and the starting position for the ^ is column 1.
Using the vale.exe from release 2.29.0 does not have this problem.
The text was updated successfully, but these errors were encountered:
Check for existing issues
Environment
Describe the bug / provide steps to reproduce it
The changes implemented by this commit causes the problem to exist: f769fcd
I have a rule that looks for incorrectly indented content. It uses the following token:
When the Markdown file contains 999 characters or more (i.e.
ctx
> 1000), the^
part of the token stops using the start of the line properly and invents (hallucinates) new starting positions.Attached are sample files that exactly show the spillover in the logic:
vale.zip
Consequently, text with four spaces before the first ` is flagged as incorrect, and the starting position for the ^ is column 1.
Using the vale.exe from release 2.29.0 does not have this problem.
The text was updated successfully, but these errors were encountered: