Skip to content
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

Convert some capital letters to lowercase and capitalize months and days in Spanish(Final) #16627

Merged
merged 4 commits into from
Mar 30, 2023

Conversation

ayazhussain79
Copy link
Contributor

@ayazhussain79 ayazhussain79 commented Mar 28, 2023

Details

We want to convert some capital characters to lowercase and capitalization for months and days in Spanish.

Fixed Issues

$ #16403
PROPOSAL: GH_LINK_ISSUE(COMMENT)

Tests

  1. Go to settings > Preferences
  2. Click on language and change it to spanish
  3. Go back > Go to Profile > personal details > Date of birth
  4. Verify that it says "Fecha de nacimiento" in the header text
  5. Open the date picker
  6. Verify the first letter in month name is in uppercase
  7. Verify that the days letters are also in uppercase
  8. Go back > Go to Home address
  9. Verify that field name "Código postal"
  10. Go back to Profile > Upload photo
  11. Select a image and click ok
  12. Verify that it says "Editar foto" in the header text
  13. Go back > Go to Workspace
  14. Select a workspace
  15. Go to Connect bank account
  16. Verify that it says "Un momento" on the loading screen header
  17. Go back to settings > Preferences
  18. Click on language and change it to english
  19. Go back > Go to Workspace
  20. Select a workspace
  21. Go to Connect bank account
  22. Verify that it says "One moment" on the loading screen header
  • Verify that no errors appear in the JS console

Offline tests

Same as above

QA Steps

Same as above

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
2023-03-25-05-02-23_IjBKQjEb.mp4

Screenshot_49
Screenshot_51
Screenshot_53
Screenshot_54
Screenshot_55

Mobile Web - Chrome Screenshot 2023-03-27 at 10 48 30 PM
Screen.Recording.2023-03-27.at.10.49.36.PM.mov
Mobile Web - Safari
Desktop Screenshot 2023-03-27 at 10 39 46 PM Screenshot 2023-03-27 at 10 38 28 PM
Screen.Recording.2023-03-27.at.10.40.34.PM.mov
Screenshot 2023-03-27 at 10 39 01 PM
iOS Screenshot 2023-03-27 at 10 45 45 PM Screenshot 2023-03-27 at 10 45 56 PM Screenshot 2023-03-27 at 10 47 17 PM
Screen.Recording.2023-03-27.at.10.46.35.PM.mov
Android Screenshot 2023-03-27 at 11 01 59 PM Screenshot 2023-03-27 at 11 02 19 PM
Screen.Recording.2023-03-27.at.11.02.56.PM.mov
Screenshot 2023-03-27 at 11 02 44 PM

@ayazhussain79 ayazhussain79 requested a review from a team as a code owner March 28, 2023 16:40
@melvin-bot melvin-bot bot requested review from luacmartins and thesahindia and removed request for a team March 28, 2023 16:40
@MelvinBot
Copy link

@luacmartins @thesahindia One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@ayazhussain79
Copy link
Contributor Author

@Julesssss @thesahindia @aldo-expensify new PR is ready for review with signed commit

@ayazhussain79 ayazhussain79 mentioned this pull request Mar 28, 2023
54 tasks
@@ -18,8 +18,8 @@ class CalendarPicker extends React.PureComponent {
constructor(props) {
super(props);

this.monthNames = moment.localeData(props.preferredLocale).months();
this.daysOfWeek = moment.localeData(props.preferredLocale).weekdays();
this.monthNames = _.map(moment.localeData(props.preferredLocale).months(), month => month.replace(/^\w/, c => c.toUpperCase()));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NAB: Just wondering why we didn't do something simpler like:

Suggested change
this.monthNames = _.map(moment.localeData(props.preferredLocale).months(), month => month.replace(/^\w/, c => c.toUpperCase()));
this.monthNames = _.map(moment.localeData(props.preferredLocale).months(), month => month.toUpperCase());

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aldo-expensify The first line of code converts the month names to title case (where the first letter of each word is capitalized), while the second line of code converts the month names to all uppercase. We just need to convert first letter of the month to uppercase

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, thanks for explaining!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was also confused by this. Could you please add a small comment explaining this for people in the future? Thanks

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean that we want sentence case for these? If so, I believe that we can use Str.recapitalize for that.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ayazhussain79, can you make this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thesahindia ok I'm going to change it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can check new change

@Julesssss Julesssss self-requested a review March 28, 2023 23:15
Copy link
Contributor

@Julesssss Julesssss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a small comment, but thanks for getting the commits signed!

@@ -18,8 +18,8 @@ class CalendarPicker extends React.PureComponent {
constructor(props) {
super(props);

this.monthNames = moment.localeData(props.preferredLocale).months();
this.daysOfWeek = moment.localeData(props.preferredLocale).weekdays();
this.monthNames = _.map(moment.localeData(props.preferredLocale).months(), month => month.replace(/^\w/, c => c.toUpperCase()));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean that we want sentence case for these? If so, I believe that we can use Str.recapitalize for that.

src/components/CalendarPicker/index.js Show resolved Hide resolved
@ayazhussain79
Copy link
Contributor Author

@thesahindia you can check the new changes

@@ -18,8 +19,8 @@ class CalendarPicker extends React.PureComponent {
constructor(props) {
super(props);

this.monthNames = moment.localeData(props.preferredLocale).months();
this.daysOfWeek = moment.localeData(props.preferredLocale).weekdays();
this.monthNames = _.map(moment.localeData(props.preferredLocale).months(), month => Str.recapitalize(month));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
this.monthNames = _.map(moment.localeData(props.preferredLocale).months(), month => Str.recapitalize(month));
this.monthNames = _.map(moment.localeData(props.preferredLocale).months(), Str.recapitalize);

NAB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aldo-expensify changed that line as suggested you can check it

@thesahindia
Copy link
Member

@ayazhussain79, the fixed issues section should look like this -

Fixed Issues

$ #16403
PROPOSAL: #16403 (comment)

And you will need to update the steps. You can check other PRs to understand how we write the steps.

  • Include the specific steps you followed to navigate to the page, rather than simply stating the name of the page.
  • Be more specific about what needs to verified.

Here's how I would write the test steps for the first two cases. You can follow the same for other cases.

  1. Go to settings > Preferences
  2. Click on language and change it to spanish
  3. Go back > Go to Profile > personal details > Date of birth
  4. Verify that it says "Fecha de nacimiento" in the header text
  5. Open the date picker
  6. Verify the first letter in month name is in uppercase
  7. Verify that the days letters are also in uppercase

Lastly I would not suggest using commit message like "This commit will do xyz". For example in your first commit, instead of writing "This commit will capitalize month and day names" you could just write "capitalize month and day names".

@ayazhussain79
Copy link
Contributor Author

@thesahindia updated fixed issues section you can check it and next time I will correct all my mistakes, Thank you

@thesahindia
Copy link
Member

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified tests pass on all platforms & I tested again on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web Screenshot 2023-03-30 at 1 57 56 AM Screenshot 2023-03-30 at 1 57 25 AM
Mobile Web - Chrome Screenshot 2023-03-30 at 1 53 41 AM Screenshot 2023-03-30 at 1 53 09 AM
Mobile Web - Safari Screenshot 2023-03-30 at 1 56 08 AM
Desktop Screenshot 2023-03-30 at 1 56 58 AM
iOS Screenshot 2023-03-30 at 1 55 37 AM
Android Screenshot 2023-03-30 at 1 51 32 AM Screenshot 2023-03-30 at 1 50 55 AM Screenshot 2023-03-30 at 1 49 50 AM

Copy link
Member

@thesahindia thesahindia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All yours @luacmartins

@thesahindia
Copy link
Member

have uploaded other platform videos/SS except Mobile Web - Safari

@ayazhussain79, what issue are you facing when using the app on iOS Safari??

Copy link
Contributor

@luacmartins luacmartins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@luacmartins
Copy link
Contributor

@Julesssss @aldo-expensify all yours

Copy link
Contributor

@Julesssss Julesssss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks all 👍

@Julesssss Julesssss merged commit 4d04aa1 into Expensify:main Mar 30, 2023
@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/Julesssss in version: 1.2.93-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 failure ❌

@OSBotify
Copy link
Contributor

OSBotify commented Apr 3, 2023

🚀 Deployed to production by https://github.com/thienlnam in version: 1.2.93-4 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants