no-danger does not report dangerouslySetInnerHTML usage in React.createElement

[nchevobbe]

The no-danger rules only reports dangerouslySetInnerHTML when it's used in JSX, but not when it's used in React.createElement

To be fair, it's mentioned in the rule description, but it took me a bit to see this.
Also, the similar no-danger-with-children rule does report usage in React.createElement, so it would be nice to be consistent here.

[ljharb]

That'd be a great enhancement.

[snakefood3232]

I see the issue with no-danger not reporting dangerouslySetInnerHTML in React.createElement, while no-danger-with-children does. I'd handle this by updating the no-danger rule to parse for createElement and apply consistent reporting logic similar to no-danger-with-children. I can have a PR up in the next 3 days. I've worked on similar ESLint rule adjustments in the past, ensuring comprehensive coverage and consistency. Looking forward to resolving this inconsistency for the community.

[ljharb]

Thanks, that'd be great. Please be sure to minimize use of LLMs in all open source contributions.