-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Please document how to make the linter fixable #467
Comments
Can you provide a reproduction that |
I just tried using the config example that remark-lint uses and notices it fixes some things. Maybe we could just amend the documentation to say "not all remark-lint rules have automatic fixers"? |
@Zemnmez That is how I would interpret the existing comment in the documentation, but if you believe it can be worded for more clarity, feel free to open a PR. |
Initial checklist
Problem
The current readme.md says this:
But it doesn't elaborate on what needs to be done to make the lint fixable. For example, currently, applying this plugin for me removed all my markdown line-wraps.
I've made the line length an error, but it doesn't appear to expose a fixer. The remark lint documentation describes some steps to achieve this, but they involve instrumenting remark-cli, something the eslint-mdx docs do not cover.
Thanks!
Solution
Markdown files should be automatically fixed.
Alternatives
Use remark-cli directly.
The text was updated successfully, but these errors were encountered: