-
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
Localization for Amount, Numbers and Dates. #3021
Localization for Amount, Numbers and Dates. #3021
Conversation
…harrajat/translations
…harrajat/translations
Please let me know If it's going in the right direction. I personally looked at all the pages and added changes. If I am missing some parts, please mention that. Thanks. There are few places where we are already using localization |
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.
This is looking good to me so far, but I'll let @iwiznia comment since he's got more context here
Oh damn, what errors? Also, make sure to regularly pull main and merge it into your branch, since it is possible some of those are already fixed. |
@iwiznia when I click Pay its was crashing the app. I have reported it and I think its being fixed. I will pull in the latest changes and check again. |
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.
Looking good
@@ -71,20 +74,20 @@ const DetailsPage = ({personalDetails, route, translate}) => { | |||
/> | |||
</View> | |||
<Text style={[styles.displayName, styles.mt1, styles.mb6]} numberOfLines={1}> | |||
{details.displayName | |||
? details.displayName | |||
: null} |
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.
So, before when details.displayName
was falsy, we would render null
, now we would render details.displayName
, is that what we want? Are there uninteded consequences of that? Mostly, I am wondering why we had this ternary condition here if there are no other consequences.
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 need to pull latest changes and I think thus this ternary would change. Why I did this as I believe we will never has a user who don't have a handle. In other words, can you imagine chating with a user who has no name(login | phone number). So if we are ended up null then we are not doing it correctly. Anyways, this issues has been fixed recently. I will pull the changes.
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 updated it so return as null when there is no displayName.
d9cd22b
to
ad470f3
Compare
Ready for review. Also pulled latest changes from Main. |
Co-authored-by: Ionatan Wiznia <iwiznia@hotmail.com>
Code looks good, can you test in all platforms and remove WIP? I will do a final review then. |
Updated. Ready to review |
@parasharrajat did you test on ios? I am not seeing the video for it. @Jag96 do you want to do one last review? |
Yeah, I tested it, I will update the video soon. |
Oh, @Jag96 is out of office, @parasharrajat if you upload the ios video test, I'll merge. |
I am having issues with my mac system but I am try to recover it and hope it will work. |
Any luck with that @parasharrajat? |
@iwiznia I'll update you today. |
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.
If I had to guess is because that's text generated in the server and not in the client. Since we don't have I18n in the server, I don't think we can fix that right now. |
Yeah. I checked the main data and see that this message is coming from backend. But I can run a search for PH number on text and replace all the instances, if you want this? |
No, I don't think we want that. We will need to solve this at some point when we add internationalization to the backend. @Jag96 any other concerns? If not, do you mind merging this? |
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.
No, I don't think we want that. We will need to solve this at some point when we add internationalization to the backend.
👍
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
Please Review @iwiznia.
Details
https://github.com/Expensify/Expensify.cash/blob/a75a4077b526417c09ed07316334a707cd2feea2/src/pages/settings/Profile/LoginField.js
Fixed Issues
Fixes #2349
Fixes #3038
Tests / QA Steps
Localization #2349
Expensify SMS Domain #3038
Tested On
Screenshots
Web / Desktop
translations.mp4
IOS
Android
1622059575660.mp4