Skip to content

feat(native): styled() on React Native - #1047

Open
owjs3901 wants to merge 1 commit into
feat/react-native-cssfrom
feat/react-native-styled
Open

owjs3901 wants to merge 1 commit into
feat/react-native-cssfrom
feat/react-native-styled

Conversation

@owjs3901

Copy link
Copy Markdown
Contributor

Part of #411, depends on #1046 (base: feat/react-native-css). PR 7 of the React Native plan: styled().

What it does

styled() compiles to a function component. The component renders its target with the styles it describes, followed by the style it is given. As the design planned, the static part is hoisted into the StyleSheet, and functions of the props become values and parts chosen at render:

export const Card = styled(Box)({ bg: '$surface', p: [2, null, 4], borderRadius: '8px' })
export const Title = styled(Text)`
  color: ${(props) => props.color};
  font-size: 18px;
`
export const Item = styled(View)({ m: 1 }, (props) => props.active && css({ opacity: 0.5 }))
export const Card = (__props) => {
  const __t = __useThemeIndex();
  const __b = __useBreakpoint();
  return <Box {...__props} style={[__s.a, [__s.b, __s.c][__t], __b < 2 ? __s.d : __s.e, __props.style]} />;
};
export const Title = (__props) => {
  return <Text {...__props} style={[__s.g, { color: ((props) => props.color)(__props) }, __props.style]} />;
};
export const Item = (__props) => {
  return <View {...__props} style={[__s.i, ((props) => props.active && __s.h)(__props), __props.style]} />;
};
  • Forms: styled(Target)(...parts), styled(Target)`css text` and styled(Target, styles).
  • Parts: the same as css() in feat(native): css() and className on React Native #1046:
    • objects with responsive values, tokens and theme/platform/orientation/press blocks;
    • conditions;
    • other css() results;
    • CSS text.
  • Functions of the props, which give variants:
    • a value: w: (p) => p.width, or an interpolation in CSS text, converted like a runtime value;
    • a part giving what css() gives: (p) => p.primary && css({...}).
  • Targets:
    • A Devup UI component renders its React Native component and keeps the styles it declares first (Flex keeps its row).
    • Any React Native or other component, such as View or Animated.View, is rendered as it is.
  • Press styles: a press style on a styled Box makes it a Pressable (feat(native): press styles through Pressable on React Native #1045). A styled Button gets a style function.
  • Hooks: the hooks the styles read, including those of css() calls inside functions, are called at the top of the generated component. styled() can therefore be called at the top of the file even when its styles differ by theme or breakpoint.
  • Imports: the styled import is removed.

Build errors

  • a tag (styled('div')), or a target that is not a component name
  • styled(Target) that is not called with styles, styled(...parts), styled used other than as a call, and styled(Target, styles, extra)
  • a function of the props that gives style props ((p) => ({ bg: p.color }), or a condition choosing such objects). React Native cannot read style props at runtime. Fix: return what css() gives, or write each value as a function.
  • a press style on a target the build cannot make a Pressable

Known difference from the web, documented in the README: <Card p={1} /> passes p on to the target instead of compiling it, because the component is not a Devup UI element. Give style or className instead.

Expo example and CI

  • apps/expo/src/Badge.tsx is now styled(Text)({...}). It still uses no runtime: check-bundle.mjs passes locally.
  • CI: feat/react-native-css is added to the pull_request branches of the workflow. It will be removed when this PR is retargeted.

Tests

  • Rust (insta + rstest) covers every form and target, including:
    • theme and breakpoint hooks in the generated component;
    • CSS text with an interpolated function;
    • function values and function parts;
    • press styles on Box and Button;
    • every error.
  • cargo test --workspace passes. There are no web snapshot changes.
  • clippy -D warnings and cargo fmt are clean.
  • Local cargo llvm-cov shows every new line covered.

#411의 일부이며 #1046에 의존합니다 (base: feat/react-native-css). React Native 계획의 7번째 PR인 styled()입니다.

변경 내용

styled()는 함수 컴포넌트로 컴파일됩니다. 이 컴포넌트는 target을 렌더링하면서 styled()가 설명하는 스타일을 적용하고, 그 뒤에 자신이 받은 style을 붙입니다. 설계대로 정적인 부분은 StyleSheet로 끌어올리고, props의 함수는 렌더링할 때 고르는 값과 부분이 됩니다(위 예시 참고).

  • 형태: styled(Target)(...parts), styled(Target)`css text`, styled(Target, styles)
  • parts: #1046의 css()와 같습니다.
    • 반응형 값, 토큰, 테마·플랫폼·방향·press 블록이 든 객체;
    • 조건식;
    • 다른 css() 결과;
    • CSS 텍스트.
  • props의 함수(variant):
    • 값: w: (p) => p.width 또는 CSS 텍스트의 보간. 런타임 값처럼 변환합니다.
    • css() 결과를 돌려주는 부분: (p) => p.primary && css({...})
  • target:
    • Devup UI 컴포넌트는 해당 React Native 컴포넌트로 렌더링하고, 먼저 선언하는 스타일을 유지합니다(Flex의 row).
    • View, Animated.View 등 그 밖의 컴포넌트는 그대로 렌더링합니다.
  • press 스타일: press 스타일이 있는 styled Box는 Pressable이 되고(feat(native): press styles through Pressable on React Native #1045), styled Button은 style 함수를 받습니다.
  • hook: 스타일이 읽는 hook은 생성된 컴포넌트 맨 위에서 호출합니다. 함수 안의 css()가 읽는 hook도 포함됩니다. 그래서 테마나 breakpoint에 따라 스타일이 달라지더라도 styled()를 파일 최상단에서 호출할 수 있습니다.
  • import: styled import는 제거됩니다.

빌드 에러

  • 태그(styled('div')) 또는 컴포넌트 이름이 아닌 target
  • 스타일과 함께 호출하지 않은 styled(Target), styled(...parts), 호출이 아닌 styled 사용, styled(Target, styles, extra)
  • style prop을 돌려주는 props 함수((p) => ({ bg: p.color }) 또는 그런 객체를 고르는 조건식). React Native는 런타임에 style prop을 읽을 수 없습니다. 해결: css() 결과를 돌려주거나, 값마다 함수로 쓰세요.
  • Pressable로 만들 수 없는 target의 press 스타일

웹과 다른 점(README에 문서화): <Card p={1} />는 p를 컴파일하지 않고 target에 그대로 넘깁니다. 이 컴포넌트는 Devup UI 요소가 아니기 때문입니다. 대신 style이나 className을 주세요.

Expo 예제와 CI

  • apps/expo/src/Badge.tsx는 이제 styled(Text)({...})입니다. 여전히 런타임을 쓰지 않으며, 로컬에서 check-bundle.mjs를 통과했습니다.
  • CI: workflow의 pull_request branches에 feat/react-native-css를 추가했습니다. 이 PR의 base를 바꿀 때 제거합니다.

테스트

  • Rust (insta + rstest)가 모든 형태와 target을 다룹니다. 여기에 포함되는 것:
    • 생성된 컴포넌트의 테마·breakpoint hook;
    • 함수를 보간한 CSS 텍스트;
    • 함수 값과 함수 부분;
    • Box와 Button의 press 스타일;
    • 모든 에러.
  • cargo test --workspace가 통과합니다. 웹 snapshot 변경은 없습니다.
  • clippy -D warnings와 cargo fmt는 깨끗합니다.
  • 로컬 cargo llvm-cov에서 새로 추가한 줄은 모두 커버됩니다.

🤖 Generated with Claude Code

`styled(Target)(...parts)`, `` styled(Target)`css text` `` and
`styled(Target, styles)` compile to a function component rendering its
target with the styles they describe, before the `style` it is given. The
parts are those of `css()`; a function in them is called with the props, as
a value or as a part giving what `css()` gives. A Devup UI target keeps the
styles it declares first, a styled `Box` with a press style becomes a
`Pressable`, and the hooks the styles read are called in the component.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codecov

codecov Bot commented Nov 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Files with missing lines Coverage Δ
libs/extractor/src/native/element.rs 100.00% <100.00%> (ø)
libs/extractor/src/native/element/css_call.rs 100.00% <100.00%> (ø)
libs/extractor/src/native/element/styled.rs 100.00% <100.00%> (ø)
libs/extractor/src/native/imports.rs 100.00% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant