Open bmitchinson opened 5 years ago
I am open to suggestions... Should we remove the rule completely or add the suggested work around?
Mostly just wanted to bring its instability into attention, could go either way. 🤷♂
Gut feeling would be to disable any rule that's not stable in all contexts.
I agree with you. It's probably wise to wait for stability.
It's been removed in 5.0.0-beta.6
.
Upstream issue still exists. Still holding on adoption for now.
Current Open Issue - Here
Wondering if that's enough to remove it from beta of v5 until it's fixed? Currently throwing unnecessary errors for
Animated.Text
components.