src/content/docs/linter/rules/use-solid-for-component.mdx
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs> <TabItem label="JavaScript (and super languages)" icon="seti:javascript"> ## Summary - Rule available since: `v2.0.0` - Diagnostic Category: [`lint/performance/useSolidForComponent`](/reference/diagnostics#diagnostic-category) - This rule isn't recommended, so you need to enable it. - This rule doesn't have a fix. - The default severity of this rule is [**information**](/reference/diagnostics#information). - This rule belongs to the following domains: - [`solid`](/linter/domains#solid) - Sources: - Inspired from [`solid/prefer-for`](https://github.com/solidjs-community/eslint-plugin-solid/blob/main/packages/eslint-plugin-solid/docs/prefer-for.md){
"linter": {
"rules": {
"performance": {
"useSolidForComponent": "error"
}
}
}
}
Enforce using Solid's <For /> component for mapping an array to JSX elements.
In Solid, <For /> component for efficiently rendering lists. Array#map causes DOM elements to be recreated.
For details on <For /> Component, see the Solid docs about Components.
let Component = (props) => <ol>{props.data.map(d => <li>{d.text}</li>)}</ol>;
let Component = (props) => <>{props.data.map(d => <li>{d.text}</li>)}</>;
let Component = (props) => (
<ol>
{props.data.map((d) => (
<li key={d.id}>{d.text}</li>
))}
</ol>
);
let Component = (props) => <ol><For each={props.data}>{d => <li>{d.text}</li>}</For></ol>;
let abc = x.map(y => y + z);
let Component = (props) => {
let abc = x.map(y => y + z);
return <div>Hello, world!</div>;
}