Avoid using children with dangerouslySetInnerHTML このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。
このルールを試す ID: tsx-react/no-danger-with-children
Language: TypeScript
Severity: Warning
Category: Error Prone
Description If both children and dangerouslySetInnerHTML are set, it’s unclear which one should take precedence, and React will throw a warning. To prevent this mistake, this rule enforces that either children or dangerouslySetInnerHTML are used, but not both.
Non-Compliant Code Examples < div dangerouslySetInnerHTML = {{ __html : "HTML" }}>{ Children }</ div >;
< Hello dangerouslySetInnerHTML = {{ __html : "HTML" }}> Children </ Hello >;
< Hello dangerouslySetInnerHTML = {{ __html : "HTML" }}>< Another /></ Hello >;
React . createElement ( "div" , { dangerouslySetInnerHTML : { __html : "HTML" } }, "Children" );
React . createElement ( "Hello" , { dangerouslySetInnerHTML : { __html : "HTML" } }, "Children" );
Compliant Code Examples < div dangerouslySetInnerHTML = {{ __html : "HTML" }} />;
< Hello dangerouslySetInnerHTML = {{ __html : "HTML" }} />;
< div > Children </ div >;
< Hello > Children </ Hello >;
React . createElement ( "div" , { dangerouslySetInnerHTML : { __html : "HTML" } });
React . createElement ( "Hello" , { dangerouslySetInnerHTML : { __html : "HTML" } });
React . createElement ( "div" , {}, "Children" );
React . createElement ( "Hello" , {}, "Children" );
Seamless integrations. Try Datadog Code Analysis
