Repository navigation
fix: A run that wraps in a list item is placed where it is - #1230
seragAhmed wants to merge 1 commit into
Conversation
mapRun searched for a run as written, but a run that wraps inside a list item or blockquote has the item's indentation or `>` after each line break in the source. The search missed it, or found a copy further down and moved the source cursor past every run after it, so their alerts were placed by searching the whole file. Place such a run with wrappedRuns, as locateWrapped already does for blocks. Fixes vale-cli#1227 Assisted-by: Claude Code
|
Before this is reviewed, please read the AI-Assisted Contributions section of the contributing guide and make sure this change meets it: you can explain every line, the description is your own and brief, it fixes a bug you hit or a feature agreed in an issue, it does not touch undocumented options, and any substantial tool use is noted. |
|
Before this can be merged, please read Vale's contributor license agreement, which is four short points, and post a new comment on this pull request whose entire text is the sentence below, with no quote, no extra words, and no trailing period. Don't use the Reply button, which quotes this comment. This is once per person, not per pull request. I have read the CLA and I agree to it You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
mapRun searched for a run as written, but a run that wraps inside a list item or blockquote has the item's indentation or
>after each line break in the source. The search missed it, or found a copy further down and moved the source cursor past every run after it, so their alerts were placed by searching the whole file. Place such a run with wrappedRuns, as locateWrapped already does for blocks.Fixes #1227
Assisted-by: Claude Code