You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could theoretically add that the getAttributes(), although, I'd like to take a guess that the RN-side prop doesn't necessarily easily map to the native equivalent (as we've seen in the past).
Nevertheless, this is definitely something we could accept as a feature.
The text was updated successfully, but these errors were encountered:
@d4vidi Thank you for your quick answer. How about borderColor attribute? Generally in the css styles we can have a lot of attributes for verification.
If we do this, we are likely to handle everything color-related. That said, CSS and native-mobile are inherently different. We will extract what we can, and cannot guarantee that borderColor and such are accessible.
I see you do validation based on attributes, and that's ok. But if you see the need to do validation as in knowing if the color is a valid HTML color at all, you can use the validate-color npm package, currently the most feature-rich HTML color validator in town. 🎨 😊
Describe your idea
We could theoretically add that the
getAttributes()
, although, I'd like to take a guess that the RN-side prop doesn't necessarily easily map to the native equivalent (as we've seen in the past).Nevertheless, this is definitely something we could accept as a feature.
The text was updated successfully, but these errors were encountered: