src/content/docs/linter/rules/no-react-specific-props.mdx
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs> <TabItem label="JavaScript (and super languages)" icon="seti:javascript"> ## Summary - Rule available since: `v1.7.2` - Diagnostic Category: [`lint/suspicious/noReactSpecificProps`](/reference/diagnostics#diagnostic-category) - This rule is **recommended**, meaning it is enabled by default. - This rule has a [**safe**](/linter/#safe-fixes) fix. - The default severity of this rule is [**warning**](/reference/diagnostics#warning). - This rule belongs to the following domains: - [`solid`](/linter/domains#solid) - [`qwik`](/linter/domains#qwik) - Sources: - Same as [`solid/no-react-specific-props`](https://github.com/solidjs-community/eslint-plugin-solid/blob/main/packages/eslint-plugin-solid/docs/no-react-specific-props.md) - Same as [`qwik/no-react-props`](https://qwik.dev/docs/advanced/eslint/#no-react-props){
"linter": {
"rules": {
"suspicious": {
"noReactSpecificProps": "error"
}
}
}
}
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.
<Hello className="John" />
<Hello class="Doe" />