Feature Request: Support has-data-* attributes on React Native

[DiegoSerra]

Hi Uniwind team 👋

First of all, great work on Uniwind — it’s a very promising styling solution for React Native, and we’re actively evaluating it for integration into our stack.

While testing, we noticed that selectors using the has-data-* pattern do not seem to work in Uniwind (native), and we wanted to ask whether this is currently unsupported or planned for future support.

Problem Statement

Selectors such as the following do not appear to be recognized or applied correctly:

has-data-[state=open]:
has-data-[active=true]:
has-data-[disabled=true]:
has-data-[slot=card-image]:

These selectors are especially important for styling parent elements based on the state of their children.

Context

Libraries like shadcn/ui rely heavily on data-* attributes and has-* selectors to enable state-based styling in headless and compound components.

Additionally, the React Native adaptation react-native-reusable follows the same architectural approach, so support for these selectors will likely become increasingly important for compatibility with this ecosystem.

Feature Request

Add support for has-data-* selectors in React Native, allowing patterns such as:

has-data-[state=open]:
has-data-[active=true]:
has-data-[disabled=true]:
has-data-[slot=card-image]:

This would enable:

• Parent-based state styling
• Proper support for headless and compound component patterns
• Better compatibility with existing and emerging UI libraries inspired by shadcn/ui

Why this matters

Support for these selectors would significantly improve interoperability with modern headless UI patterns and make Uniwind a more viable drop-in styling solution for advanced component libraries.

If this is already planned, it would be great to know the expected timeline. Happy to help test or provide feedback if needed.

Thanks again for the great work on Uniwind 🚀

[Brentlok]

Hi there! 👋

Thanks for the kind words and the detailed breakdown of why these selectors are important

In short:

We currently do not support parent-based styling (including has-data-* patterns) in Uniwind.

However, we recognize the value this adds for handling complex component states. We have added this feature to our "Nice-to-Have" list for future consideration as we continue to evolve the library.

Thanks again for the feedback and for helping us improve Uniwind! 🚀