check-param-names should have a contexts option like the rest of the rules do

[Zamiell]

I believe that check-param-names should have a contexts option like the rest of the rules do.
That fact that it does not already have this seems to be an oversight.
Please implement this; it should be a simple fix!

This is needed in order to get a lint error for the following common situation:

/**
 * @param barr This is the description of bar. Oops, we misspelled "bar" as "barr".
 */
declare function foo(bar: number) {}

[brettz9]

I don't think we want to consider this as an oversight with there being no custom contexts for this rule and other function-only rules because checking all of the function contexts is intended and should be sufficient.

However, we were missing TSDeclareFunction as a default context to check, causing the sample code not to be reported as expected. That is now fixed.

[gajus]

🎉 This issue has been resolved in version 39.3.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀