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
require-description-complete-sentence: Add an option to specify abbreviations #424
Labels
Comments
Having the same issue. For the sake of example:
Should be (but gets wrongly corrected):
Loving this plugin, great job! |
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Dec 27, 2019
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Dec 27, 2019
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Dec 28, 2019
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Dec 28, 2019
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Dec 29, 2019
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Dec 29, 2019
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Dec 31, 2019
brettz9
added a commit
that referenced
this issue
Dec 31, 2019
🎉 This issue has been resolved in version 18.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I often use abbreviations such as
i.e.
ore.g.
in my comments. The rulerequire-description-complete-sentence
requires that these abbreviations are followed by an uppercase letter. It would be great to have a rule option to indicate which abbreviations we currently use and are terminated by a period which may not be followed by an uppercase.The text was updated successfully, but these errors were encountered: