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
Update for changes in remark, remark-lint #25
Comments
@wooorm as there was no reaction by the original author are you considering to fork this rule into being one of the official ones? I would really appreciate to use it. |
@ThomDietrich Hi! 👋 I don’t feel this should be part of the core of remark-lint: sentence-detection is just too hard a problem.
Does that help? |
Hey @wooorm 👋 I already thought that this is the issue. I could look into this project but it will probably take me a few minutes. Hoped to benefit from your offer "If you want, I can do the updates" - maybe @why-jay wants to have another look? I will also look into remark-retext, thanks for the hint! Thanks for your prompt and informative answer! |
I can help convert and maintain a bit, but I’m already owning too many repo’s to take the lead on a fork! |
Hi! 👋
remark-lint recently changed (and so did remark). Each rule is now a separate package published to npm, for example, take the
final-newline
rule, which is nowremark-lint-final-newline
.You can find more info on what changed on the release pages for remark and remark-lint, but they may be lacking as I’m working hard on upgrading the ecosystem first.
There’s a package,
unified-lint-rule
, that you can (should!) depend on to make rules though.remark-lint-strong-marker
, also a good example, uses it to accept options.To use “rules”, you must install all rules you want to use, for example:
And then specify them in your config file like so:
...on the API you can do the following:
Finally, feel free to drop by in Gitter room, or reply below, to ask any questions you may have!
P.S. When done, could you create a PR for remark-lint to include this in the list of external rules?
P.P.S. If you want, I can do the updates, if you add me as a collab on this repo and on npm!
The text was updated successfully, but these errors were encountered: