noReactSpecificProps
Это содержимое пока не доступно на вашем языке.
Summary
Section titled “Summary”- Rule available since:
v1.7.2 - Diagnostic Category:
lint/suspicious/noReactSpecificProps - This rule has a safe fix.
- The default severity of this rule is warning.
- This rule belongs to the following domains:
- Sources:
- Same as
solidjs/no-react-specific-props
- Same as
How to configure
Section titled “How to configure”{ "linter": { "rules": { "suspicious": { "noReactSpecificProps": "error" } } }}Description
Section titled “Description”Prevents React-specific JSX properties from being used.
This rule is intended for use in JSX-based frameworks (such as Qwik, Solid, etc.) that do not use React-style prop names.
Examples
Section titled “Examples”Invalid
Section titled “Invalid”<Hello className="John" />code-block.jsx:1:8 lint/suspicious/noReactSpecificProps FIXABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚠ This JSX attribute is specific to React.
> 1 │ <Hello className=“John” />
│ ^^^^^^^^^
2 │
ℹ This attribute may not be supported by non-React frameworks, as it is not native to HTML.
> 1 │ <Hello className=“John” />
│ ^^^^^^^^^
2 │
ℹ Safe fix: Replace this attribute name with “class”
1 │ - <Hello·className=“John”·/>
1 │ + <Hello·class=“John”·/>
2 2 │
<Hello class="Doe" />Related links
Section titled “Related links”Copyright (c) 2023-present Biome Developers and Contributors.