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

Added count param to phrase param and return plural form accordingly #48229

Merged
merged 48 commits into from
Sep 26, 2024

Conversation

ZhenjaHorbach
Copy link
Contributor

@ZhenjaHorbach ZhenjaHorbach commented Aug 28, 2024

Details

This PR added a count parameter to the phrase parameter to return the plural form when necessary. Also In this PR we
updated the types to support PluralizeValues and refactored the code so that all translation functions now use a single object containing all the necessary parameters

Fixed Issues

#38614
PROPOSAL:

Tests

  1. Open App
  2. Open few screens and verify that the translations are displayed correctly.
  • Verify that no errors appear in the JS console

Offline tests

  1. Open App
  2. Open few screens and verify that the translations are displayed correctly.

QA Steps

  1. Open App
  2. Open few screens and verify that the translations are displayed correctly.
  • 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: mWeb Chrome
    • iOS: Native
    • iOS: mWeb 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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 grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • 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 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(theme.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 the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • 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.

Screenshots/Videos

Android: Native
android.mov
Android: mWeb Chrome
android-web.mov
iOS: Native
ios.mov
iOS: mWeb Safari
ios-web.mov
MacOS: Chrome / Safari
web.mov
MacOS: Desktop
desktop.mov


type TranslationBase = {[key: string]: TranslationBaseValue | TranslationBase};
// eslint-disable-next-line @typescript-eslint/no-explicit-any
type ArgumentType<T, R> = T extends (arg: infer A, ...args: any[]) => R ? A : unknown;
Copy link
Contributor

Choose a reason for hiding this comment

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

@ZhenjaHorbach Can you explain this please?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's just helper type
Which I used for checking first parameter

And basically it is used to determine the type of the first parameter
And if the first parameter is not an object
We will get a TS error

@ZhenjaHorbach ZhenjaHorbach marked this pull request as ready for review August 30, 2024 16:00
@ZhenjaHorbach ZhenjaHorbach requested a review from a team as a code owner August 30, 2024 16:00
Copy link

melvin-bot bot commented Aug 30, 2024

@shubham1206agra Please 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]

@melvin-bot melvin-bot bot removed the request for review from a team August 30, 2024 16:00
@ZhenjaHorbach ZhenjaHorbach requested a review from a team as a code owner September 3, 2024 07:06
@ZhenjaHorbach
Copy link
Contributor Author

@shubham1206agra
Could you please check PR ?
Thanks

@dubielzyk-expensify
Copy link
Contributor

Assume this needs no design review? If so, let me know and I'll check it out :)

@ZhenjaHorbach
Copy link
Contributor Author

Assume this needs no design review? If so, let me know and I'll check it out :)

Oh sorry 😅
Looks like after I updated the branch to the last main Design label appeared
But in this PR there are no style changes

But thanks !

@shubham1206agra
Copy link
Contributor

@ZhenjaHorbach Have you enforced the single parameter condition in function in translation? Since I was able to add another parameter without any errors.

@ZhenjaHorbach
Copy link
Contributor Author

@shubham1206agra
Yes
Could you provide example ?

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Sep 5, 2024

Here is an example

Снимок экрана 2024-09-05 в 10 30 37

@ZhenjaHorbach
Copy link
Contributor Author

@iwiznia
We have only Changed files ESLint check issues
But we can ignore them
Plus they are not related to our changes

Copy link
Contributor

@iwiznia iwiznia left a comment

Choose a reason for hiding this comment

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

So we are removing the possibility to call translate('bla', 'param', 'other'). That's fine, but my fear is that other unmerged PRs could be using that format and we would not catch that, right?

Can you update the links in https://github.com/Expensify/App/#internationalization and add a small explanation of the pluralization feature?

phraseKey: TKey,
fallbackLanguage: 'en' | 'es' | null = null,
...phraseParameters: PhraseParameters<Phrase<TKey>>
path: TPath,
Copy link
Contributor

Choose a reason for hiding this comment

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

FWIW I think I liked more phraseKey then path, NAB

return translatedPhrase(...phraseParameters);
/**
*
* is Plain object is for checking if the phraseTranslated output
Copy link
Contributor

Choose a reason for hiding this comment

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

is Plain object is is this referring to a method or what?

phraseTranslated

I think you mean translatedPhrase?

/**
*
* is Plain object is for checking if the phraseTranslated output
* is an object then further check if it include the count param or not
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
* is an object then further check if it include the count param or not
* is an object then further check if it includes the count param or not

*
* is Plain object is for checking if the phraseTranslated output
* is an object then further check if it include the count param or not
* OR before checking the plain object output, we can check if we have the count
Copy link
Contributor

Choose a reason for hiding this comment

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

Not 100% what exactly is the counterpart of this OR... the last if here, both last ifs?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh
Sorry
These were draft comments 😅
I agree that they should be updated

}

const phraseObject = parameters[0];
if (phraseObject && typeof phraseObject === 'object' && 'count' in phraseObject && typeof phraseObject.count === 'number') {
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we need to check 'count' in phraseObject since if count is not defined, typeof would return undefined and this code would work anyway

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think we need some additional clarification to prevent Property 'count' does not exist on type 'object'.

Copy link
Contributor

Choose a reason for hiding this comment

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

Can't we change the type of phraseObject to allow for an optional count?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think we can do it
But I'm not sure that is a good idea update TranslationParameters type for count
Plus we use such a condition to write count key into phraseObject

Снимок экрана 2024-09-25 в 22 35 02 Снимок экрана 2024-09-25 в 22 34 35

Copy link
Contributor

Choose a reason for hiding this comment

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

But I'm not sure that is a good idea update TranslationParameters type for count

Why?

Plus we use such a condition to write count key into phraseObject

Which we could remove if we added it as an optional param, no?

if (phraseObject && typeof phraseObject === 'object' && 'count' in phraseObject && typeof phraseObject.count === 'number') {
const pluralRule = new Intl.PluralRules(language).select(phraseObject.count);

const pluralResult = pluralRule in translateResult && translateResult[pluralRule];
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need the pluralRule in translateResult I think the code would work exactly the same without it, no?

return translateResult.other(phraseObject.count);
}

throw new Error(`Invalid plural form for '${path}'`);
Copy link
Contributor

Choose a reason for hiding this comment

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

Throw early (ie: invert this if condition and throw)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think it's ok !
Because this error symbolizes that all the previous conditions were not pass
As esle

Copy link
Contributor

Choose a reason for hiding this comment

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

What all previous conditions? There's only one of them.
We prefer early throw/return in general, as it makes the code easier to read and follow

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated !

@iwiznia iwiznia removed the request for review from a team September 25, 2024 19:49
@iwiznia
Copy link
Contributor

iwiznia commented Sep 25, 2024

Oh, can you also pick some existing translation, for example these ones and change them to use the new pluralization methods?
Just to leave as an example in real code.
I think I will create a new issue later to remove all usages of Str.pluralize which should not be needed anymore

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Sep 25, 2024

So we are removing the possibility to call translate('bla', 'param', 'other'). That's fine, but my fear is that other unmerged PRs could be using that format and we would not catch that, right?

Can you update the links in https://github.com/Expensify/App/#internationalization and add a small explanation of the pluralization feature?

Actually a good question
But I think that this is not critical
Since in this case only TS will break on main after merging PR with wrong format of translates

@shubham1206agra
Copy link
Contributor

Oh, can you also pick some existing translation, for example these ones and change them to use the new pluralization methods? Just to leave as an example in real code. I think I will create a new issue later to remove all usages of Str.pluralize which should not be needed anymore

This will be done by me in #45892

@iwiznia
Copy link
Contributor

iwiznia commented Sep 26, 2024

Since in this case only TS will break on main after merging PR with wrong format of translates

Not sure I follow. Are you saying that if you call translate(key, 'one', 'two') it would still work?

This will be done by me in #45892

Ah nice!

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Sep 26, 2024

Since in this case only TS will break on main after merging PR with wrong format of translates

Not sure I follow. Are you saying that if you call translate(key, 'one', 'two') it would still work?

Yes
Since this pattern does not affect the new pluralization in any way, it will work the same as before
Provided that the translation will look like this

key: (one, two)=>${one}${two}

But this is expected
Since in the current typing on main in the case of a translation function we return only a string

Снимок экрана 2024-09-26 в 17 16 58

@iwiznia
Copy link
Contributor

iwiznia commented Sep 26, 2024

Yes

Ah nice, thanks for checking and explaining!

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Sep 26, 2024

Ah nice, thanks for checking and explaining!

And I fixed other comments 😃
So if you have no more questions
We can move on !

deleteRates: ({count}: DistanceRateOperationsParams) => `Delete ${Str.pluralize('rate', 'rates', count)}`,
deleteRates: () => ({
one: 'Delete rate',
other: () => `Delete rates`,
Copy link
Contributor

Choose a reason for hiding this comment

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

Why is this a function?

Copy link
Contributor

Choose a reason for hiding this comment

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

Since it will be easy to implement, and we need to pass the count somehow.

Copy link
Contributor

Choose a reason for hiding this comment

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

But same as the others, you could just have a string here right?

Copy link
Contributor Author

@ZhenjaHorbach ZhenjaHorbach Sep 26, 2024

Choose a reason for hiding this comment

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

Yes
I also thought about it 5 minutes ago 😅
I will merge changes soon

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Now it will work!

Comment on lines +634 to +642
messages: () => ({
zero: 'No messages',
one: 'One message',
two: 'Two messages',
few: (count) => `${count} messages`,
many: (count) => `You have ${count} messages`,
other: (count) => `You have ${count} unread messages`,
})

Copy link
Contributor

Choose a reason for hiding this comment

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

Oh crap, did not really notice this before... does the object containing the messages always need to be a function or can it also be:

Suggested change
messages: () => ({
zero: 'No messages',
one: 'One message',
two: 'Two messages',
few: (count) => `${count} messages`,
many: (count) => `You have ${count} messages`,
other: (count) => `You have ${count} unread messages`,
})
messages: {
zero: 'No messages',
one: 'One message',
two: 'Two messages',
few: (count) => `${count} messages`,
many: (count) => `You have ${count} messages`,
other: (count) => `You have ${count} unread messages`,
}

There's really no need for a function there...

Copy link
Contributor

@shubham1206agra shubham1206agra Sep 26, 2024

Choose a reason for hiding this comment

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

No, since it will be impossible to differentiate between messages and messages.one translation key in a flat object.

Copy link
Contributor Author

@ZhenjaHorbach ZhenjaHorbach Sep 26, 2024

Choose a reason for hiding this comment

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

This implementation looks like any other object with translations
And not a specific translation with plural forms

Copy link
Contributor

Choose a reason for hiding this comment

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

No, since it will be impossible to differentiate between messages and messages.one translation key in a flat object.

I don't get this

This implementation looks like any other object with translations
And not a specific translation with plural forms

Yeah, so?

Anyway, it would be nice if we supported the simple object notation too, but not going to block on that since this is a big PR, we've been waiting a long time for it and adding the function is not that bad.

deleteRates: ({count}: DistanceRateOperationsParams) => `Eliminar ${Str.pluralize('tasa', 'tasas', count)}`,
deleteRates: () => ({
one: 'Eliminar tasa',
other: () => `Eliminar tasas`,
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here

iwiznia
iwiznia previously approved these changes Sep 26, 2024
@ZhenjaHorbach
Copy link
Contributor Author

@iwiznia
Sorry about the last commit 😅
I fixed that comment

If everything is ok, could you approve it again and merge it?

@iwiznia
Copy link
Contributor

iwiznia commented Sep 26, 2024

We are skipping ESLint checks because this PR is touching 76 unrelated files and fixing all the previously existing lint errors would make this PR riskier.

Thanks so much for this, great job!!!

@iwiznia iwiznia merged commit 04b82bc into Expensify:main Sep 26, 2024
17 of 18 checks passed
Copy link

melvin-bot bot commented Sep 26, 2024

@iwiznia looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

@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.

Copy link
Contributor

🚀 Deployed to staging by https://github.com/iwiznia in version: 9.0.41-0 🚀

platform result
🤖 android 🤖 cancelled 🔪
🖥 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.

6 participants