solid-errors-react-contamination

Destructuring props breaks SolidJS reactivity by losing the reactive getter proxies, causing values to resolve once without tracking updates. Use splitProps or direct prop access to preserve signal tracking.

Fix React contamination in SolidJS by replacing destructured props with splitProps, swapping Array.map rendering with the For component, and wrapping conditionals in the Show component to restore reactive updates.

React contamination in a SolidJS migration occurs when React idioms like Array.map rendering or improper signal usage silently degrade reactivity. Static code reviews detect these anti-patterns to enforce SolidJS-compliant patterns.

Using Array.map to render lists in SolidJS is a React contamination anti-pattern that breaks reactivity. Use the For component instead to ensure list items update reactively without destroying and recreating DOM nodes.

Yes, this SolidJS anti-pattern detection suits automated tooling scans and manual code reviews. It enforces detection rules via frontmatter metadata and references to catch destructured props and improper signal usage.

Use the Show component instead of ternary or logical AND conditional rendering in SolidJS to prevent React contamination. Show preserves reactivity by managing DOM mounting without evaluating conditions prematurely.