Rule Change: Extend no-empty-definitions to cover empty footnote definitions

[TKDev7]

What rule do you want to change?

no-empty-definitions

What change do you want to make?

Generate more warnings

How do you think the change should be implemented?

A new default behavior

Example code

<!-- should be reported as empty -->
[^note]:

What does the rule currently do for this code?

Does not report [^note]: as empty.

What will the rule do after it's changed?

Reports [^note]: as empty footnote definition.

Participation

• I am willing to submit a pull request to implement this change.

Additional comments

No response

[nzakas]

Thanks for the suggestion. I think this may be useful, and I'm not sure if this should be an option or a separate rule. I'm kind of leaning towards a separate rule.

@eslint/eslint-team thoughts?

[JoshuaKGoldberg]

Agreed, this would be useful. I'm also not strongly opinionated on whether the rules should be combined. 🤷

[nzakas]

It looks like no-duplicate-definitions applies to both definitions and footnote definitions, so to keep things consistent it seems like we should add this as an option to no-empty-definitions instead of having a different rule.

Marking as accepted.