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

Fix: Inconsistent capitalization in product #17327

Conversation

dukenv0307
Copy link
Contributor

@dukenv0307 dukenv0307 commented Apr 12, 2023

Details

Inconsistent capitalization in product

Fixed Issues

$ #17239
PROPOSAL: #17239 (comment)

Tests

Note: Case 1 in test could be only tested in desktop web and desktop app

  • The 'C' should be small in the tooltip for the call icon
  1. Login with any account
  2. Go to any chat
  3. Hover call icon
  4. Verify that the content of tooltip is "Start a call"
  • Text in Transfer Balance modal should be consistent capitalization and the header in Choose Transfer Account modal "A" should be in small letters
  1. Login with any account
  2. Go to Setting > Payments > Transfer balance if account has balance or go to url '/settings/payments/transfer-balance' if else
  3. Verify that the header in this modal is 'Transfer balance'
  4. Verify that option 1 is "Instant (Debit card)"
  5. Verify that option 2 is "1-3 Business days (Bank account)"
  6. Verify that the text that below two option is "Which account"
  7. Select any option to go to Choose Transfer Account modal
  8. Verify that the header in this modal is 'Choose account'
  • "Terms of Service" and "Privacy" text should be consistent in product
  1. Go to login page
  2. Enter the email of your account and click continue
  3. In the page to enter the password, verify that the term text is "By logging in, you agree to the Terms of Service and Privacy."
  4. Enter your password to login
  5. After login successfully, go to Setting > About
  6. Verify that the content in footer is "Read the Terms of Service and Privacy"
  7. Switch to Spanish language
  8. Go to Setting > Workspaces > Connect bank account
  9. In step 1, doesn't check to checkbox and click Continue button
  10. Verify that error message "Debes aceptar los Términos de Servicio para continuar" is displayed below checkbox
  • The header in the Delete Account modal "A" should be in small letters
  1. Login with any account
  2. Go to Setting > Payments
  3. Select a payment method to delete
  4. Verify that the header in the Delete account modal is "Delete account"
  • Uploading Attachment... message "A" should be in small letters
  1. Login with any account
  2. Go to any chat
  3. Upload a attachment
  4. Verify that Uploading attachment message is 'Uploading attachment'
  • Error in add bank account form should be consistent capitalization
  1. Login with any account
  2. Open Setting > Workspaces
  3. Open any workspaces
  4. Open connect bank account
  5. Click on connect manually
  6. In step 1, without filling any detail, click on continue
  7. Verify that the error message of Routing number field is "Please enter a valid routing number"
  8. Verify that the error message of Account number is "Please enter a valid account number"
  9. Fill in detail in step one with valid value, accept terms and click continue to go to step 2 (i.e routin no = 123456780, account no = 123456789)
  10. In step 2, without filling any detail, click on save & continue
  11. Verify that the error message of Tax ID number field is "Please enter a valid tax ID number"
  12. Verify that the error message of Company type is "Please enter a valid company type"
  13. Verify that the error message of Company address is "Please enter a valid street address that is not a PO box"
  • Verify that no errors appear in the JS console

Offline tests

Same above

QA Steps

Note: Case 1 in test could be only tested in desktop web and desktop app

  • The 'C' should be small in the tooltip for the call icon
  1. Login with any account
  2. Go to any chat
  3. Hover call icon
  4. Verify that the content of tooltip is "Start a call"
  • Text in Transfer Balance modal should be consistent capitalization and the header in Choose Transfer Account modal "A" should be in small letters
  1. Login with any account
  2. Go to Setting > Payments > Transfer balance if account has balance or go to url '/settings/payments/transfer-balance' if else
  3. Verify that the header in this modal is 'Transfer balance'
  4. Verify that option 1 is "Instant (Debit card)"
  5. Verify that option 2 is "1-3 Business days (Bank account)"
  6. Verify that the text that below two option is "Which account"
  7. Select any option to go to Choose Transfer Account modal
  8. Verify that the header in this modal is 'Choose account'
  • "Terms of Service" and "Privacy" text should be consistent in product
  1. Go to login page
  2. Enter the email of your account and click continue
  3. In the page to enter the password, verify that the term text is "By logging in, you agree to the Terms of Service and Privacy."
  4. Enter your password to login
  5. After login successfully, go to Setting > About
  6. Verify that the content in footer is "Read the Terms of Service and Privacy"
  7. Switch to Spanish language
  8. Go to Setting > Workspaces > Connect bank account
  9. In step 1, doesn't check to checkbox and click Continue button
  10. Verify that error message "Debes aceptar los Términos de Servicio para continuar" is displayed below checkbox
  • The header in the Delete Account modal "A" should be in small letters
  1. Login with any account
  2. Go to Setting > Payments
  3. Select a payment method to delete
  4. Verify that the header in the Delete account modal is "Delete account"
  • Uploading Attachment... message "A" should be in small letters
  1. Login with any account
  2. Go to any chat
  3. Upload a attachment
  4. Verify that Uploading attachment message is 'Uploading attachment'
  • Error in add bank account form should be consistent capitalization
  1. Login with any account
  2. Open Setting > Workspaces
  3. Open any workspaces
  4. Open connect bank account
  5. Click on connect manually
  6. In step 1, without filling any detail, click on continue
  7. Verify that the error message of Routing number field is "Please enter a valid routing number"
  8. Verify that the error message of Account number is "Please enter a valid account number"
  9. Fill in detail in step one with valid value, accept terms and click continue to go to step 2 (i.e routin no = 123456780, account no = 123456789)
  10. In step 2, without filling any detail, click on save & continue
  11. Verify that the error message of Tax ID number field is "Please enter a valid tax ID number"
  12. Verify that the error message of Company type is "Please enter a valid company type"
  13. Verify that the error message of Company address is "Please enter a valid street address that is not a PO box"
  • 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 code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • 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
  • The 'C' should be small in the tooltip for the call icon

Screenshot from 2023-04-13 11-17-44

  • Text in Transfer Balance modal should be consistent capitalization and the header in Choose Transfer Account modal "A" should be in small letters

Screenshot from 2023-04-19 13-15-26

Screenshot from 2023-04-13 11-18-14

  • "Terms of Service" and "Privacy" text should be consistent in product

Screenshot 2023-04-19 20:33:47

Screenshot from 2023-04-19 13-16-53

Screenshot from 2023-04-13 17-16-49

Screenshot 2023-04-19 20:43:44

  • The header in the Delete Account modal "A" should be in small letters

Screenshot from 2023-04-13 11-18-44

  • Uploading Attachment... message "A" should be in small letters

Screenshot from 2023-04-13 11-19-06

  • Error in add bank account form should be consistent capitalization

Screenshot from 2023-04-19 13-17-32

Screenshot from 2023-04-19 13-19-05

Mobile Web - Chrome
  • Text in Transfer Balance modal should be consistent capitalization and the header in Choose Transfer Account modal "A" should be in small letters

1681885657864

1681360352276

  • "Terms of Service" and "Privacy" text should be consistent in product

1681911393388

1681885657831

1681381549926

1681912092191

  • The header in the Delete Account modal "A" should be in small letters

1681360352490

  • Uploading Attachment... message "A" should be in small letters

1681360352243

  • Error in add bank account form should be consistent capitalization

1681885657898

1681885657928

1681885657591

Mobile Web - Safari
  • Text in Transfer Balance modal should be consistent capitalization and the header in Choose Transfer Account modal "A" should be in small letters
Screenshot 2023-04-13 at 17 40 44 Screenshot 2023-04-19 at 14 28 05
  • "Terms of Service" text should be consistent in product
Screenshot 2023-04-19 at 14 28 34 Screenshot 2023-04-19 at 20 52 59 Screenshot 2023-04-19 at 20 52 15 Screenshot 2023-04-13 at 17 41 58
  • The header in the Delete Account modal "A" should be in small letters
Screenshot 2023-04-13 at 17 47 02
  • Uploading Attachment... message "A" should be in small letters
Screenshot 2023-04-13 at 17 47 52
  • Error in add bank account form should be consistent capitalization
Screenshot 2023-04-19 at 14 31 23 Screenshot 2023-04-19 at 14 31 38
Desktop
  • The 'C' should be small in the tooltip for the call icon
Screenshot 2023-04-13 at 17 54 11
  • Text in Transfer Balance modal should be consistent capitalization and the header in Choose Transfer Account modal "A" should be in small letters
Screenshot 2023-04-19 at 14 38 10 Screenshot 2023-04-13 at 17 55 15
  • "Terms of Service" and "Privacy" text should be consistent in product
Screenshot 2023-04-19 at 14 38 26 Screenshot 2023-04-19 at 20 55 38 Screenshot 2023-04-19 at 20 55 54 Screenshot 2023-04-13 at 17 57 08
  • The header in the Delete Account modal "A" should be in small letters
Screenshot 2023-04-13 at 17 59 03
  • Uploading Attachment... message "A" should be in small letters
Screenshot 2023-04-13 at 17 59 38
  • Error in add bank account form should be consistent capitalization
Screenshot 2023-04-19 at 14 39 33 Screenshot 2023-04-19 at 14 39 40
iOS
  • Text in Transfer Balance modal should be consistent capitalization and the header in Choose Transfer Account modal "A" should be in small letters
Screenshot 2023-04-19 at 14 54 14 Screenshot 2023-04-13 at 17 49 33
  • "Terms of Service" and "Privacy" text should be consistent in product
Screenshot 2023-04-19 at 14 54 21 Screenshot 2023-04-19 at 21 06 36 Screenshot 2023-04-19 at 21 06 57 Screenshot 2023-04-13 at 17 50 46
  • The header in the Delete Account modal "A" should be in small letters
Screenshot 2023-04-13 at 17 51 15
  • Uploading Attachment... message "A" should be in small letters
Screenshot 2023-04-13 at 17 51 45
  • Error in add bank account form should be consistent capitalization
Screenshot 2023-04-19 at 14 55 12 Screenshot 2023-04-19 at 14 55 05
Android
  • Text in Transfer Balance modal should be consistent capitalization and the header in Choose Transfer Account modal "A" should be in small letters

Screenshot_1681888165

image_2023_04_13T09_03_39_201Z

  • "Terms of Service" and "Privacy" text should be consistent in product

Screenshot_1681911632

Screenshot_1681886818

image_2023_04_13T09_18_21_294Z

Screenshot_1681911879

  • The header in the Delete Account modal "A" should be in small letters

image_2023_04_13T09_09_02_946Z

  • Uploading Attachment... message "A" should be in small letters

image_2023_04_13T09_33_15_043Z

  • Error in add bank account form should be consistent capitalization

Screenshot_1681888184

Screenshot_1681888204

Screenshot_1681888206

@dukenv0307 dukenv0307 marked this pull request as ready for review April 13, 2023 11:07
@dukenv0307 dukenv0307 requested a review from a team as a code owner April 13, 2023 11:07
@melvin-bot melvin-bot bot requested review from 0xmiros and thienlnam and removed request for a team April 13, 2023 11:07
@MelvinBot
Copy link

@thienlnam @0xmiroslav 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]

@@ -930,7 +930,7 @@ function buildOptimisticAddCommentReportAction(text, file) {
const commentText = getParsedComment(text);
const isAttachment = _.isEmpty(text) && file !== undefined;
const attachmentInfo = isAttachment ? file : {};
const htmlForNewComment = isAttachment ? 'Uploading Attachment...' : commentText;
const htmlForNewComment = isAttachment ? 'Uploading attachment...' : commentText;
Copy link
Contributor

Choose a reason for hiding this comment

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

@thienlnam should we localize this for Spanish? I think this place is fine for now because we'll be deprecating uploading message.
https://expensify.slack.com/archives/C01GTK53T8Q/p1664819628960309

Copy link
Contributor

Choose a reason for hiding this comment

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

Nice catch, yeah I'm not sure why this copy was not ever localized. Agree we can just leave it since we're going to be removing it soon

@dukenv0307 dukenv0307 force-pushed the fix/17239-inconsistent-capitalization-in-product branch from f210d08 to f3cfbce Compare April 13, 2023 16:49
src/languages/es.js Outdated Show resolved Hide resolved
@0xmiros
Copy link
Contributor

0xmiros commented Apr 13, 2023

And don't force-push

@dukenv0307 dukenv0307 force-pushed the fix/17239-inconsistent-capitalization-in-product branch from f3cfbce to a007c2c Compare April 13, 2023 16:53
@dukenv0307
Copy link
Contributor Author

dukenv0307 commented Apr 13, 2023

@0xmiroslav Noted, thanks for reminding me. Please help to check again

@dukenv0307
Copy link
Contributor Author

dukenv0307 commented Apr 18, 2023

@0xmiroslav @thienlnam Please help to check this PR and ping me if there are any problems.

@0xmiros
Copy link
Contributor

0xmiros commented Apr 18, 2023

Still waiting for confirmation - #17239 (comment)

@thienlnam
Copy link
Contributor

Sasha left some confirmation - let's also make sure to address the cases in the latest merged issue, this should address all the inconsistent capitalization in product

@dukenv0307
Copy link
Contributor Author

dukenv0307 commented Apr 19, 2023

@thienlnam @0xmiroslav I just updated the PR, please help to check again and I will update screenshots after your confirmation

@0xmiros
Copy link
Contributor

0xmiros commented Apr 19, 2023

@dukenv0307 confirmed. please go ahead screenshots

@dukenv0307
Copy link
Contributor Author

@0xmiroslav I just updated all screenshot, help to check again

@0xmiros
Copy link
Contributor

0xmiros commented Apr 19, 2023

@dukenv0307 on which platform can I see Spanish changes?

@0xmiros
Copy link
Contributor

0xmiros commented Apr 19, 2023

@dukenv0307 please pull from main. Branding changed on Login page

@dukenv0307
Copy link
Contributor Author

@0xmiroslav Spanish changes only in case "Terms of Service" and "Privacy" text should be consistent in product and you can see it in all platform

@dukenv0307
Copy link
Contributor Author

@0xmiroslav Login page changed in main but this text is same. Do I need to update screenshots in login page

@0xmiros
Copy link
Contributor

0xmiros commented Apr 19, 2023

@0xmiroslav Login page changed in main but this text is same. Do I need to update screenshots in login page

yes please

@0xmiros
Copy link
Contributor

0xmiros commented Apr 19, 2023

@dukenv0307 did you update?

@dukenv0307
Copy link
Contributor Author

@0xmiroslav sorry I was busy earlier, I will update it right now

@dukenv0307
Copy link
Contributor Author

@0xmiroslav I just updated. Help to check again

@0xmiros
Copy link
Contributor

0xmiros commented Apr 19, 2023

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 grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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 code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • 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 web-attach web-bank1 web-bank2 web-delete web-start web-transfer Screenshot 2023-04-19 at 3 48 52 PM Screenshot 2023-04-19 at 3 49 03 PM Screenshot 2023-04-19 at 3 49 36 PM Screenshot 2023-04-19 at 3 49 52 PM Screenshot 2023-04-19 at 3 50 25 PM Screenshot 2023-04-19 at 3 50 44 PM Screenshot 2023-04-19 at 3 52 09 PM
Mobile Web - Chrome mchrome-term mchrome-term2
Mobile Web - Safari msafari-bank1 msafari-bank2 msafari-term
Desktop desktop-attach desktop-bank1 desktop-bank2 desktop-delete desktop-start desktop-transfer
iOS ios-about ios-delete
Android android-bank1 android-bank2 android-term

0xmiros
0xmiros previously approved these changes Apr 19, 2023
Copy link
Contributor

@0xmiros 0xmiros left a comment

Choose a reason for hiding this comment

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

2 minor concerns:

  • Inconsistency - (Debit card), (Bank account) is missing in Spanish. This is not capitalization issue so out of scope.

Screenshot 2023-04-19 at 4 41 35 PM

Screenshot 2023-04-19 at 4 42 15 PM

  • Terms of Service and Privacy capitalization together in a sentence (already raised in linked issue but got no answer yet)

Screenshot 2023-04-19 at 4 44 31 PM

Screenshot 2023-04-19 at 4 44 38 PM

Other than that, looks good.
cc: @thienlnam

thienlnam
thienlnam previously approved these changes Apr 19, 2023
Copy link
Contributor

@thienlnam thienlnam left a comment

Choose a reason for hiding this comment

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

Looks good! Thanks for the review, going to wait for confirmation but I agree with your stance on the capitalization

@0xmiros
Copy link
Contributor

0xmiros commented Apr 21, 2023

@dukenv0307 minor one:
Sole Proprietorship -> Sole proprietorship

incorporation type

@dukenv0307 dukenv0307 dismissed stale reviews from thienlnam and 0xmiros via 1534e19 April 21, 2023 03:08
@dukenv0307
Copy link
Contributor Author

@0xmiroslav I just fixed, please check again

Copy link
Contributor

@0xmiros 0xmiros left a comment

Choose a reason for hiding this comment

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

Thanks for the quick fix. We're still waiting for "Terms of Service and Privacy" confirmation before final merge.

Copy link
Contributor

@thienlnam thienlnam left a comment

Choose a reason for hiding this comment

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

Cool we're good to go here! Nice work everyone

@thienlnam thienlnam merged commit ab669ad into Expensify:main Apr 21, 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/thienlnam in version: 1.3.4-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.4-0 🚀

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.

5 participants