[Change request] valid-jsdoc's matchDescription should support multiple regular expressions and different error messages for each.

currently matchDescription accepts a regexp and throws an error message of “JSDoc description does not satisfy the regex pattern.”

Instead, I suggest it will accept a few regexpes, and will allow for different error messages. For example:

"valid-jsdoc": [
    "error",
    {
        "matchDescription": {
            ".+": "Missing JSDoc  description.",
            "^\\s*[A-Z]": "JSDoc description should start with an uppercase letter.",
            "\\.\\s*$": "JSDoc description must end with a period.",
            "^(?![\\s\\S]*?\\.\\s*[a-z]).*$": "Sentence in JSDoc description must start with an uppercase letter."
        }
    }
]

This will allow for a greater usability of the matchDescription option.

If it’s not a priority for the team, I can open a pull request myself, as my project needs it. If this would not get accepted, I will write a rule with the same behavior for my project anyway.

Edit: forgot to mention, it would also be nice to have an option to apply these to param descriptions. Such that we can check they start with an hyphen, end with a period, etc.

[nzakas]

Thanks for the suggestion. As of yesterday, we have decided to officially end-of-life JSDoc support in ESLint. All JSDoc features are now deprecated and we won’t be fixing bugs or making any further improvements to those features.

We are recommending that people transition over to use the eslint-plugin-jsdoc plugin instead of the built-in rules in ESLint.

Thanks for understanding and we apologize for any inconvenience.

[platinumazure]

Removing myself as champion due to lack of general interest in this issue from the team and the community.