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
Was there a conscious decision to exclude attribute/cti from the react-native transform group? It is currently the only transform group that does not leverage the transform, which led to some initial confusion about why some of my filters weren’t behaving as expected across platforms.
If this was an oversight, could it be added to the transform group? I understand that this is easy to work around and presumably has some breaking change implications, but maybe it's worth considering in the next major for consistency across other groups.
Cheers!
The text was updated successfully, but these errors were encountered:
I don't recall this to be a conscious decision, we'd have to dig through git blames to find which PR added the transformGroup, in v3 it was also there without the attribute/cti.
If it was an oversight, then I'm definitely down to add "attribute/cti" so it's consistent with the others, I would consider that a bugfix then which I'm okay with putting in v4 even if it is technically a small breaking change.
Hi all 👋
Was there a conscious decision to exclude
attribute/cti
from thereact-native
transform group? It is currently the only transform group that does not leverage the transform, which led to some initial confusion about why some of my filters weren’t behaving as expected across platforms.If this was an oversight, could it be added to the transform group? I understand that this is easy to work around and presumably has some breaking change implications, but maybe it's worth considering in the next major for consistency across other groups.
Cheers!
The text was updated successfully, but these errors were encountered: