-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False positive warnings #6
Comments
@AlexWayfer please include the actual error when opening bug reports. |
Sorry, of course, my bad. The output is:
You can see it in the mentioned PR and, more detailed, in the CI task: https://cirrus-ci.com/task/6656178379816960 So, here not only auto-links, but also |
A regression in the autolink parser has cause cases where links inside of links happen.
is interpreted as
which is why rules around links and link references are currently breaking. pinning |
Oh, thank you! Sorry for bothering. |
No worries, it's a quirky bug that shows up in some unexpected ways. |
Subject of the issue
I have wrong warnings.
Your environment
npm
6.14.11.Steps to reproduce
Faced with it here: AlexWayfer/sequel-enum_values#56
rm -r node_modules/
, but I can withrm package-lock.json
.The difference is:
Expected behavior
No warnings for a file without offenses.
Actual behavior
Warnings somewhy, with the same versions of
remark
andremark-gfm
, as I see, but, I guess, with different indirect dependencies versions.I report here, in
remark-gfm
, because there are warning only from it and it has its own dependencies.The text was updated successfully, but these errors were encountered: