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
Based on the tokens I've created, I would expect on line 6 the final "and" to be flagged by Vale. It is instead flagging an earlier, non-final, instance of "and."
When I open this session in regex101, it creates this pattern (?i)(?m)(?:and$|or$|[;,]$), and the pattern-matching works as expected, flagging the final "and".
Check for existing issues
Environment
Describe the bug / provide steps to reproduce it
Vale Studio Session: https://studio.vale.sh/s/d3c237c0d55224013966f836931cb453
Based on the tokens I've created, I would expect on line 6 the final "and" to be flagged by Vale. It is instead flagging an earlier, non-final, instance of "and."
When I open this session in regex101, it creates this pattern
(?i)(?m)(?:and$|or$|[;,]$)
, and the pattern-matching works as expected, flagging the final "and".This seems related possibly to Issue 646.
Thank you!
The text was updated successfully, but these errors were encountered: