Files
HausApp/.agents/skills/vercel-react-native-skills/rules/rendering-no-falsy-and.md
René Schober 4e34270786 initial commit
2026-03-13 06:23:06 +01:00

75 lines
1.8 KiB
Markdown

---
title: Never Use && with Potentially Falsy Values
impact: CRITICAL
impactDescription: prevents production crash
tags: rendering, conditional, jsx, crash
---
## Never Use && with Potentially Falsy Values
Never use `{value && <Component />}` when `value` could be an empty string or
`0`. These are falsy but JSX-renderable—React Native will try to render them as
text outside a `<Text>` component, causing a hard crash in production.
**Incorrect (crashes if count is 0 or name is ""):**
```tsx
function Profile({ name, count }: { name: string; count: number }) {
return (
<View>
{name && <Text>{name}</Text>}
{count && <Text>{count} items</Text>}
</View>
);
}
// If name="" or count=0, renders the falsy value → crash
```
**Correct (ternary with null):**
```tsx
function Profile({ name, count }: { name: string; count: number }) {
return (
<View>
{name ? <Text>{name}</Text> : null}
{count ? <Text>{count} items</Text> : null}
</View>
);
}
```
**Correct (explicit boolean coercion):**
```tsx
function Profile({ name, count }: { name: string; count: number }) {
return (
<View>
{!!name && <Text>{name}</Text>}
{!!count && <Text>{count} items</Text>}
</View>
);
}
```
**Best (early return):**
```tsx
function Profile({ name, count }: { name: string; count: number }) {
if (!name) return null;
return (
<View>
<Text>{name}</Text>
{count > 0 ? <Text>{count} items</Text> : null}
</View>
);
}
```
Early returns are clearest. When using conditionals inline, prefer ternary or
explicit boolean checks.
**Lint rule:** Enable `react/jsx-no-leaked-render` from
[eslint-plugin-react](https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/jsx-no-leaked-render.md)
to catch this automatically.