fix: allow string style prop on non-host elements in dom/no-string-style-prop, closes #1217

[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	Sep 6, 2025 10:26pm

[Copilot]

Pull Request Overview

This pull request fixes a bug in the dom/no-string-style-prop ESLint rule to allow string style props on non-host elements (custom React components) while still enforcing the rule for DOM elements.

• Added a host element check to only enforce the rule on actual DOM elements
• Added test case to verify custom components can use string style props

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
no-string-style-prop.ts	Added host element check to restrict rule enforcement to DOM elements only
no-string-style-prop.spec.ts	Added test case validating that custom components can use string style props

---

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