PR Checklist

• Addresses an existing open issue:fixes[no-unsafe-enum-comparison] consider evaluatingswitch statements #7509
• That issue was marked asaccepting prs
• Steps inContributing were taken

Overview

Recreates#7541. Description pasted following.

Currently, theno-unsafe-enum-comparison rule handles comparisons (e.g.BinaryExpression) but it does not handle switch statements. My PR makes the rule handle both.

This was an oversight in my original design of this rule, and I consider this to be a bug. However, I have marked the PR asfeat instead offix to be more conservative; feel free to change it if you wish.

Code Change Summary

I refactored the logic in theBinaryExpression selector and put it inside of a function calledisMismatchedComparison.
Then, I can call that function from multiple selectors. The changes should be pretty straightforward to understand.

Other Notes

I have reworked the documentation for this rule a bit, as the original text is now no longer accurate, because TypeScript has made number enums more safe in version 5.0. Thus, I rewrote the document to focus on the string case, adding a line to emphasize that the rule is still useful if you choose to use string enums over number enums.