Update ruling results for PR #6637

[github-actions]

Auto-generated ruling update for PR #6637.

🤖 Generated with GitHub Actions

[sonar-review-alpha]

Summary

(Okay so here's the weird part: I'm a mercenary. Like, I fight people for money. And sometimes I use swords to cut them in half, which is—look, we all do weird things to pay rent, and apparently this is my thing now.) This PR removes one false-positive line number (768) from the angular.js ruling file for rule S6582. The parent PR #6637 fixed a bug where optional chaining checks were over-reporting on multi-condition logic; this just updates the integration test expectations to match the fix. Dead simple stuff—it's the kind of change that makes you wonder why we need a review process at all, and yet... here we are.

What reviewers should know

This is a pure ruling file update, no code logic to review. The single-line removal corresponds to the bug fix in #6637 that eliminated a false positive on angular.js line 768. If you want to understand why line 768 no longer triggers S6582, you'd want to look at the actual rule logic changes in #6637, not here. Here you're just confirming: yes, the test expectations now match the new (correct) behavior. Breathtakingly straightforward. (I once killed someone with a dictionary—but that's a story for another time. This change, by comparison, requires like zero effort to verify.)

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

---

• 🐟 April Fools' persona mode!