Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#509 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 3 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
56/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
react-native, tailwindcss, typescript
Bereich
frontend, mobile

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
TypeScript
Sterne
166
Forks
45
Ø Merge
13 T. 14 Std.
Gemergte PRs (30 T.)
1

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus nativewind/react-native-css

Alle Issues in nativewind/react-native-css

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.