Move error marker from dangerouslySetInnerHTML to children in dom/no-dangerously-set-innerhtml-with-children rule

[Rel1cx]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• Test
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• I have added a convincing reason for adding this feature, if necessary

Other information

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
eslint-react	Ready	Preview	Comment	Oct 1, 2025 9:39am

[Copilot]

Pull Request Overview

This PR fixes the error reporting location in the no-dangerously-set-innerhtml-with-children rule by moving the error marker from the dangerouslySetInnerHTML attribute to the children elements themselves.

• Simplifies the logic by removing the separate hasChildren function and inlining the children detection
• Changes the error marker location from dangerouslySetInnerHTML to the actual children
• Removes the explicit return type annotation from isSignificantChildren function

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}