Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

origin-* classes: would you take a PR for transformOrigin now, or after 5.0?

Aberta
  • Algo errado?
#509 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 3 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
56/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
react-native, tailwindcss, typescript
Domínio
frontend, mobile

Direção de pesquisa

Read the compatibility notes for the NativeWind v5 RC and inspect how origin-* classes are currently handled in react-native-css. The issue gives a reproduction using origin-top-left rotate-45 and the expected transformOrigin behavior on iOS and Android. Confirm whether a PR is wanted for the 5.0 release before starting; done means the class maps to the expected style and the behavior is covered on both platforms.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Before submitting a new issue
  • I tested using the latest version of the library, as the bug might be already fixed.
  • I tested using a supported version of react native.
  • I checked for possible duplicate issues, with possible answers.
  • I checked that React Native supports the styles I am using.
  • If using animations/transitions, I checked that React Native Reanimated supports the styles I am using.
Bug summary

More a question than a bug. We use react-native-css through the NativeWind v5 RC in our Expo app.

origin-top-left rotate-45 rotates around the center on iOS and Android, because the origin part is dropped. React Native has supported transformOrigin since 0.73, and style={{ transformOrigin: "top left", transform: [{ rotate: "45deg" }] }} rotates around the corner as expected. Checked on React Native 0.86.3, iOS 26.5 simulator and Android 17 emulator.

I saw it's listed as not supported in the RC compatibility notes, and that the v4 PR nativewind/nativewind#1126 was closed. Would you take a PR that maps the origin-* classes to transformOrigin now, or would you rather wait until after 5.0? Either is fine with me, the style prop works in the meantime.

Tailwind CSS classes
<View className="origin-top-left rotate-45" />
// style on iOS and Android: { transform: [{ rotateZ: "45deg" }] }
// expected: the same, plus a transformOrigin for the top left corner
Environment info
  npmPackages:
    react: 19.2.3 => 19.2.3
    react-native: 0.86.3 => 0.86.3
    react-native-css: 3.1.0-rc.0 => 3.1.0-rc.0
    tailwindcss: 4.1.12 => 4.1.12
Linguagem predominante
TypeScript
Estrelas
166
Forks
45
Merge médio
13d 14h
PRs com merge (30d)
1

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de nativewind/react-native-css

Todas as issues de nativewind/react-native-css

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.