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
I searched issues and couldn’t find anything (or linked relevant results below)
Affected packages and versions
retext-repeated-words@4.2.0
Link to runnable example
No response
Steps to reproduce
Background: I was testing to see how well this plugin worked in the spellchecker-cli package when I ran into an unexpected assertion error. The expression Well, it it doesn’t have to to be. Like a fish in the\r\nthe sea. didn't catch the repeated the. Being highly interested in what was causing it; I eventually traced it back to this package and reproduced my example in the local test folder.
It hadn't even been caught as an error. I expect it didn't read the \r\n as a whitespace character and maybe need to be take it up with people behind the nlcst package if my suspicions are correct.
Expected behavior
There should have been three strings in the messages array in the example like there is with the \n example.
Affected runtime and version
node@16.14.0
Affected package manager and version
npm@8.5.0
Affected OS and version
Windows 10
Build and bundle tools
Other (please specify in steps to reproduce)
The text was updated successfully, but these errors were encountered:
Initial checklist
Affected packages and versions
retext-repeated-words@4.2.0
Link to runnable example
No response
Steps to reproduce
Background: I was testing to see how well this plugin worked in the spellchecker-cli package when I ran into an unexpected assertion error. The expression
Well, it it doesn’t have to to be. Like a fish in the\r\nthe sea.
didn't catch the repeatedthe
. Being highly interested in what was causing it; I eventually traced it back to this package and reproduced my example in the local test folder.I made my local test.js look like the following: https://pastebin.com/ibNziPtb
It had failed. Here is a screenshot.
It hadn't even been caught as an error. I expect it didn't read the \r\n as a whitespace character and maybe need to be take it up with people behind the
nlcst
package if my suspicions are correct.Expected behavior
There should have been three strings in the messages array in the example like there is with the \n example.
Affected runtime and version
node@16.14.0
Affected package manager and version
npm@8.5.0
Affected OS and version
Windows 10
Build and bundle tools
Other (please specify in steps to reproduce)
The text was updated successfully, but these errors were encountered: