-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD for payment 2022-09-26] [$250] User can't use , (comma) In spanish for decimals during IOU - reported by @thesahindia #9497
Comments
Triggered auto assignment to @isabelastisser ( |
Triggered auto assignment to @joelbettner ( |
Triggered auto assignment to @kevinksullivan ( |
@kevinksullivan reassigning you b/c I think @joelbettner unassigned you on accident 😅 |
Just adding that we believe this already exists for the send/request money flows, so that code likely offers some guidance. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel ( |
Triggered auto assignment to @sketchydroide ( |
@thesahindia please apply for reporting. Thanks! |
Proposal:
And I agree with that since I've also tried pressing I'm proposing we allow user to use both
const decimalNumberRegex = new RegExp(/^\d+([,.]\d{0,2})?$/, 'i');
onPress={() => this.props.onStepComplete(this.state.amount.replace(',', '.'))}
Result: cinnamon-20220625-1.mp4UPD
RATE_VALUE: /^\d{1,8}([,.]\d{0,3})?$/,
updateRateValue(value) {
const numValue = parseFloat(value.replace(',', '.'));
if (_.isNaN(numValue)) {
return;
}
const rateToDisplay = value.includes(',') ? numValue.toFixed(3).replace('.', ',') : numValue.toFixed(3);
this.setState({
rateValue: rateToDisplay,
});
Policy.setCustomUnitRate(this.props.policyID, this.state.unitID, {
customUnitRateID: this.state.rateID,
name: this.state.rateName,
rate: numValue.toFixed(3) * 100,
}, null);
} Result: cinnamon-20220625-2.mp4On a side note, I personally think that updating input's value so that the number always has 3 digits after the separator looks suboptimal (notice that on the video). We could just delete |
@eVoloshchak PR has been reverted. |
Started working on the PR. However, if someone was to have a phone set to English with a New Expensify app set Spanish, that would create a problem. What should I do here? |
@eVoloshchak Lets get others thoughts on slack can you create a thread there. |
Created a thread here |
@eVoloshchak How/which Spanish language did you set to get this keyboard with a comma, can you share the recording for the same? |
cinnamon-20220805-10.mp4 |
But I'm not seeing a comma there, Simulator.Screen.Recording.-.iPhone.13.-.2022-08-08.at.22.31.00.mp4 |
@eVoloshchak Bump Any update on this issue |
It seems like a consensus has been achieved:
So we accept both signs on IOS and only the correct one on Android. I'll submit a PR shortly |
PR is up |
This issue has not been updated in over 15 days. @sketchydroide, @eVoloshchak, @kevinksullivan, @Santhosh-Sellavel eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
PR in review. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.1-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2022-09-26. 🎊 |
@kevinksullivan bump! |
Paid @Santhosh-Sellavel and @eVoloshchak |
@thesahindia please accept this reposted job to get paid for reporting. |
Applied to the job. Thanks. |
@kevinksullivan Can you close this issue and the other issue #10108 as this same problem mentioned here #9497 (comment) and it is fixed now, thanks! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
User should be able to use comma, also the decimal should change to comma after changing the language to spanish.
Actual Result:
User can't use comma
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.77-0

Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @thesahindia
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1655491691902889
Job: https://www.upwork.com/jobs/~0174a215853c604f4d
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: