-
Notifications
You must be signed in to change notification settings - Fork 121
[WCiOS17] Update .onchange() usage to iOS17 API v2
#16080
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
[WCiOS17] Update .onchange() usage to iOS17 API v2
#16080
Conversation
Generated by 🚫 Danger |
|
👋 @RafaelKayumov @itsmeichigo adding you both to review since is mostly related to Kiwi features, one review is enough. Does not need to go into 23.2, can wait till next release. |
|
|
|
Version |
itsmeichigo
left a comment
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.
Thanks for updating this 🥇
I did smoke test on some of the more obvious paths: product creation AI, Blaze, and shipping labels. Some changes are more related to POS like FormattableAmountTextField and the measureHeight and measureFrame modifiers, so it'd be nice if you could double check those.
|
Thanks for the review!
Sure thing, I tested those on my end and I saw no issues 👍 |

Part of WOOMOB-1003
Continuation from #16002
Description
This PR addresses the remaining warnings related to the
.onChangeusage across Kiwi features (sort of), by moving them to use the new iOS17+ API.The previous API has been updated and deprecated from forcing us to use 1 parameter, to instead:
All changes are a refactor, so no behavior should be changed. Most of times we either don't care about the value and just react to it, or we care about
newValueonly.Testing information
Screenshots
N/A