-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[styles] Outdated warning message #25637
Conversation
@oliviertassinari How is this code used internally i.e. can we add a test case? It's not clear whether this is relevant to old or new styling engine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@eps1lon It's legacy at this point (old). I have proposed that we fix it to reduce confusion during the migration period of v5, for the one year or two to come.
Should we add a test case? I personally fail to see the long term value for this area of the codebase but if the author can provide it, it would be better
so can this be merged? thanks for the approval @oliviertassinari |
@bhairavee23 Could you look into adding a test case? :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added a test case.
@mnajdova At first, I thought that we could add this warning back into the new solution. But looking closer at the implementation, it doesn't seem possible because of the dynamic props.
@bhairavee23 Thanks 👍 |
Closes #25559