-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Fix interactive dialog number handling #8431
Conversation
I have done a round of testing on this for the iOS build.
Tested only on iOS for now. There is an external service failing preventing Android builds at the moment. |
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.
Tested and passed based on QA Testing above.
Android will be tested post merge so we can process with creating a release while we wait for for Android builds to be functional again.
Cherry pick is scheduled. |
(cherry picked from commit 32453b3)
/cherry-pick release-2.24 |
Cherry pick is scheduled. |
(cherry picked from commit 32453b3)
(cherry picked from commit 32453b3) Co-authored-by: Daniel Espino García <[email protected]>
(cherry picked from commit 32453b3) Co-authored-by: Daniel Espino García <[email protected]>
Summary
The handling of the number field was not done right for a long time. We were passing a number value to the text input
value
property, which was completely ignoring it (since it was not a string).The changes we did to be more coherent with the types surfaced the issue, by showing
NaN
in the input when we removed completely the number.This PR solves that, and makes sure we only send on the submission proper numbers, and not the empty string for number values.
Ticket Link
Fix https://mattermost.atlassian.net/browse/MM-62334
Release Note