Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Class name doubles in component with style set to array

未关闭
#1,860 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
react-native, tailwindcss, typescript
领域
mobile

调研方向

Start from the reproduction repository linked in the issue and the two wrapper components in the snippet, Text2 (style passed as an array) and Text3 (style passed as an object). Compare how className is resolved in each case to find where the previous value is kept. Done when the rendered element carries only the current class names in both cases, and the fix is confirmed by the repro app.

由索引模型根据 Issue 内容生成。

描述

Describe the bug
I have a custom component Text2 which assigns classname and also sets the style to an array of styles. This leads to the classname having both the current and previous value in the html.

Reproduction

The component Text2 will behave wrong. The component Text3 will behave correctly.

import {Text as RNText} from 'react-native';

export const Text2: React.FC<any> = ({ className, children }) => {
    return <RNText className={className} style={[{ textAlign: 'center' }]}>{children}</RNText>;
};

export const Text3: React.FC<any> = ({ className, children }) => {
    return <RNText className={className} style={{ textAlign: 'center' }}>{children}</RNText>;
};

...

<Text2
    className={`${activeTab === index ? 'text-red-500' : 'text-yellow-500'}`}
>
    {tab}
</Text2>
<Text3
    className={`${activeTab === index ? 'text-red-500' : 'text-yellow-500'}`}
>
    {tab}
</Text3>

https://github.com/user-attachments/assets/fc16e25f-a05f-48e8-a90d-d9cebad2fc56

Repro: https://github.com/denniske/nativewind-textcomponent-repro

Expected behavior
Just have the current classname assigned to the html div.

"nativewind": "^4.2.1",
"react-native": "0.81.4",
"expo": "^54.0.0",
主要语言
JavaScript
星标
8.1k
派生
409
平均合并
1 天 15 小时
30 天内合并 PR
1

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nativewind/nativewind 的其他 Issue

查看 nativewind/nativewind 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。