require-description shouldn't require a description for eslint-enable

[DetachHead]

when using eslint-enable, there's already an eslint-disable comment with the description on it so there's no reason to provide another description when re-enabling it.

describe('any', () => {
    /* eslint-disable @typescript-eslint/no-explicit-any -- testing the any type */
    test('pass', () => {
        exactly<any>()(any)
    })
    test('fail', () => {
        // @ts-expect-error doesn't match
        exactly<any>()(number)
        // @ts-expect-error doesn't match
        exactly<number>()(any)
    })
    /* eslint-enable @typescript-eslint/no-explicit-any -- testing the any type */
})

original issue: mysticatea#61

[dimitropoulos]

this seems the same as: mysticatea#49

which is to say: I 100% agree!

[tylerlaprade]

I have always used it like this, using this config:
"eslint-comments/require-description": ["error", { "ignore": ["eslint-enable"] }],

[github-actions]

This issue has been automatically closed because we haven't received a response from the original author 🙈. This automation helps keep the issue tracker clean from issues that aren't actionable. Please reach out if you have more information for us! 🙂