-
Notifications
You must be signed in to change notification settings - Fork 581
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
MarkdownBear: use remark-lint to report meaningful messages #926
Comments
So, the introduction of Rather urgently, we need to test what happens with remark reformats and remark-lint emits an error. I expect both will happen, resulting in duplication of sorts, which may be confusing. |
With reference to
I've tested that both happen and there is a duplication. i.e. |
One workaround can be to avoid using duplicated settings, i.e. higher preference should be given to code correcting capabilities instead of |
Using the revised output of remark is helpful for tidying the markdown automatically, however that means there are no descriptions of the problems.
The remark-lint plugin reports error messages.
When in CI mode, and the tidying of the file is useless, and descriptive messages are critical.
e.g. https://github.com/imsky/PocketEuler/blob/master/.travis.yml
The text was updated successfully, but these errors were encountered: