fix: show error message depend on the language preference #19324

StevenKKC · 2023-05-19T22:23:38Z

Details

Fixed Issues

$ #18203
PROPOSAL: #18203(COMMENT)

Tests

Go Preference
Set offline
Change the language to Spanish
Click on new chat with invalid number, example +15005550111
Send messages
Go back to Preference, change the language to English
Go to the same chat again and set online
Verify that the error messages is shown in English when the language was already changed to English.

The error message should be shown in English

Offline tests

QA Steps

Same as Tests step.

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)
In web and desktop version, there's a console error that is not related to this PR. A console error is generated in src/styles/getTooltipStyles.js and src/libs/BootSplash/index.js, and display error screen.
I think should open an issue for it.
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 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

web.mov

Mobile Web - Chrome

mobile.web.chrome.mp4

Mobile Web - Safari

mobile.web.safari.mov

Desktop

desktop.mov

iOS

iOS.mov

Android

Android.mp4

github-actions · 2023-05-19T22:23:51Z

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

melvin-bot · 2023-05-19T22:24:07Z

@amyevans 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]

fedirjh

@StevenKKC As this is your first time contribution , you need to sign the CLA , check this #19324 (comment) . Also please update the checklist , the template should’ve been maintained . There are some lint error that you should fix as well.

Please include all screenshots for all platforms.

fedirjh · 2023-05-19T23:30:33Z

src/components/DotIndicatorMessage.js

@@ -64,7 +65,7 @@ const DotIndicatorMessage = (props) => {
                        key={i}
                        style={styles.offlineFeedback.text}
                    >
-                        {message}
+                        {Localize.translateError(message)}


Suggested change

{Localize.translateError(message)}

{message}

Let's move this to line 51 as bellow :

const sortedMessages = _.chain(props.messages) .keys() .sortBy() .map((key) => props.messages[key]) // Using uniq here since some fields are wrapped by the same OfflineWithFeedback component (e.g. WorkspaceReimburseView) // and can potentially pass the same error. .uniq() .map((message) => Localize.translateError(message)) .value();

fedirjh · 2023-05-19T23:40:02Z

src/libs/Localize/index.js

@@ -91,6 +91,24 @@ function translateLocal(phrase, variables) {
    return translate(BaseLocaleListener.getPreferredLocale(), phrase, variables);
 }

+/**
+ * Return translated message for phrase.


Suggested change

* Return translated message for phrase.

* Return translated string for given error

fedirjh · 2023-05-19T23:53:30Z

src/libs/actions/BankAccounts.js

@@ -81,7 +81,7 @@ function getVBBADataForOnyx() {
                value: {
                    isLoading: false,
                    errors: {
-                        [DateUtils.getMicroseconds()]: Localize.translateLocal('paymentsPage.addBankAccountFailure'),


I think we can extract this part to ErrorUtils.js as below :

/** * Method used to generate errors object for optimistic * @param {String} error - error key or message to be saved * @return {Object} - Object to be optimistically saved to Onyx * */ function getOptimisticErrors(error){ return ({[DateUtils.getMicroseconds()]: error}); } // Use It as errors: ErrorUtils.getOptimisticErrors('paymentsPage.addBankAccountFailure'),

@fedirjh @chiragsalian @StevenKKC We're passing 'paymentsPage.addBankAccountFailure' to the utility method, but all it's doing is storing that key as the error instead of translating it. So this is what the error looks like:

but it should be:

1685721717986000: "An unexpected error occurred while trying to add your bank account. Please try again."

@luacmartins Yes , We save the key then we translate it inside DotIndicatorMessage.js

App/src/components/DotIndicatorMessage.js

Line 52 in 465b788

.map((message) => Localize.translateIfPhraseKey(message))

We check if the key exists in the translation directory , then we translate it , If it's from backend then it will be displayed as it it's

App/src/libs/Localize/index.js

Lines 100 to 106 in 465b788

function translateIfPhraseKey(phrase) {

try {

return translateLocal(phrase);

} catch (error) {

return phrase;

}

}

Is there any issue with that ?

@luacmartins Storing the key is correct, and when display that error message, the key will be translated to the message.

We're only calling translateIfPhraseKey in DotIndicator, but there are other places displaying the error text, e.g. Forms, that don't use DotIndicator.

Oh! We missed that case.

@luacmartins should we raise a new PR to address that or should we revert ?

This is in prod already, so it's a regression and we should raise a PR to fix it.

cc @luacmartins I have raised a draft PR #20093 , can you please check it

StevenKKC · 2023-05-20T00:19:29Z

I have read the CLA Document and I hereby sign the CLA

fedirjh · 2023-05-20T01:50:39Z

@StevenKKC Please fix the failing tests as well , you need to update them with the new approach.

StevenKKC · 2023-05-20T12:55:16Z

@fedirjh Updated.
Sorry, I'm not pay attention to many things.
I have fixed lint errors, and according to your suggestion, added a utility function. Please review again.
Android screenshot and mobile chrome screenshot, I'll upload a little later.

fedirjh · 2023-05-21T19:14:59Z

@StevenKKC Can you please merge main. Please update tests step as well

Notice that the error messages is shown in Spanish even when the language was already changed to English in offline mode.

Verify that the error messages is shown in English when the language was already changed to English.

fedirjh · 2023-05-21T20:22:38Z

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

Mobile Web - Chrome

Chrome.mov

Mobile Web - Safari

Safari.mov

Desktop

Desktop.mov

iOS

IOS.mov

Android

Android.mov

fedirjh · 2023-05-21T20:26:12Z

Android screenshot and mobile chrome screenshot, I'll upload a little later.

@StevenKKC The changes look good. Please include the missing screenshots and address my comment #19324 (comment)

StevenKKC · 2023-05-22T06:03:24Z

@fedirjh Uploaded the missing screenshots and tests step.

fedirjh

Looks good to me.

cc @chiragsalian

🎀👀🎀 C+ reviewed

StevenKKC · 2023-05-22T16:26:23Z

@fedirjh Thanks for your review.

@chiragsalian Could you please review my PR?

StevenKKC · 2023-05-22T20:09:10Z

@fedirjh @chiragsalian Because of conflict, I have merged main branch into my branch.

StevenKKC · 2023-05-22T23:33:17Z

@chiragsalian Updated files according to your suggestion.

StevenKKC · 2023-05-23T02:58:52Z

@chiragsalian @fedirjh All checks have passed. What can I do for this now?

StevenKKC · 2023-05-23T05:07:40Z

@chiragsalian Could you please review the changes that you requested? I hope to merge this PR as soon as possible.

chiragsalian

Yup i wanted to discuss this solution with my team so it took me a bit.

Looks like you missed a spot here and here.

Other than that code LGTM. i left some minor suggestion just to improve readability.

src/libs/ErrorUtils.js

StevenKKC · 2023-05-23T18:48:54Z

@chiragsalian I have updated files according to your request. Could you please review again?

chiragsalian

I think you missed addressing this comment of mine.
Specifically this one,

Looks like you missed a spot here and here.

fedirjh · 2023-05-23T19:10:07Z

There is an extra eslint comment here on line 43 that should be removed as well

StevenKKC · 2023-05-23T19:27:12Z

@chiragsalian @fedirjh Updated.

StevenKKC · 2023-05-23T19:52:31Z

@chiragsalian All checks have passed. Please let me know what I should do.

chiragsalian

LGTM

chiragsalian · 2023-05-23T20:06:48Z

I'm going ahead and merging since fedi already approved it earlier and his most recent review comment was minor.

OSBotify · 2023-05-23T20:13:46Z

✋ 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 · 2023-05-25T00:34:39Z

🚀 Deployed to staging by https://github.com/chiragsalian in version: 1.3.18-0 🚀

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

OSBotify · 2023-05-25T01:08:11Z

🚀 Deployed to staging by https://github.com/chiragsalian in version: 1.3.18-0 🚀

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

OSBotify · 2023-05-25T01:30:07Z

🚀 Deployed to staging by https://github.com/chiragsalian in version: 1.3.18-0 🚀

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

OSBotify · 2023-05-26T07:07:19Z

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.3.18-2 🚀

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

StevenKKC · 2023-05-26T18:45:16Z

I have checked the Deploy checklist (#19565) and the issue #19651 (#19651).

But I think it's not related to this PR at all.

When user change the language preference, the following code will be executed.

App/src/libs/actions/App.js

Lines 85 to 112 in 0f1188d

    
           function setLocale(locale) { 
        
               if (locale === preferredLocale) { 
        
                   return; 
        
               } 
        
               // If user is not signed in, change just locally. 
        
               if (!currentUserAccountID) { 
        
                   Onyx.merge(ONYXKEYS.NVP_PREFERRED_LOCALE, locale); 
        
                   return; 
        
               } 
        
               // Optimistically change preferred locale 
        
               const optimisticData = [ 
        
                   { 
        
                       onyxMethod: Onyx.METHOD.MERGE, 
        
                       key: ONYXKEYS.NVP_PREFERRED_LOCALE, 
        
                       value: locale, 
        
                   }, 
        
               ]; 
        
               API.write( 
        
                   'UpdatePreferredLocale', 
        
                   { 
        
                       value: locale, 
        
                   }, 
        
                   {optimisticData}, 
        
               ); 
        
           }

In the offline mode (or the user have already changed the force offline mode to online, but the app is still in the offline status, as you can see in your video), API.write only change the local Onyx data, and the request API that update the language preference does not send to the server.

After send the comment, the server will send the response error message and the Onyx data that is stored in the server to the app, and these data will contain the original language preference, as you can see in the below screenshot.

So, after app receive the server response and merge the server's Onyx data, the language preference will be changed to the previous state, that is Spanish, and the error message is shown in Spanish.

That is, this PR is working as expected.

And now, there is a new issue opened.

fedirjh · 2023-05-26T19:11:46Z

@StevenKKC you should post that in the the other issue. That would be helpful to identify the root cause of the other issue, And if we find that the root cause is related to this PR , then we can flag it as regression and proceed with a fix.

Edit : I agree with your analysis , this issue is not related to the changes with this PR

fix: show error message depend on the language preference

17cf288

StevenKKC requested a review from a team as a code owner May 19, 2023 22:23

melvin-bot bot removed the request for review from a team May 19, 2023 22:24

melvin-bot bot requested a review from amyevans May 19, 2023 22:24

StevenKKC mentioned this pull request May 19, 2023

[PAID] [$1000] The error is displayed in Spanish on invalid number chat even when the language preference has changed to English #18203

Closed

6 tasks

amyevans requested review from chiragsalian and fedirjh May 19, 2023 22:49

amyevans assigned StevenKKC May 19, 2023

amyevans removed their request for review May 19, 2023 22:49

fedirjh suggested changes May 19, 2023

View reviewed changes

fedirjh reviewed May 19, 2023

View reviewed changes

fix lint error & add getOptimisticErrors utility function

78bf158

StevenKKC requested a review from fedirjh May 20, 2023 13:12

fedirjh approved these changes May 21, 2023

View reviewed changes

fedirjh previously approved these changes May 22, 2023

View reviewed changes

Merge branch 'main' into stevenkkc-fixErrorMessage

c2912a1

StevenKKC dismissed fedirjh’s stale review via c2912a1 May 22, 2023 20:05

StevenKKC requested a review from fedirjh May 22, 2023 20:09

remove Localize import in Policy.js

4bda64b

StevenKKC requested a review from chiragsalian May 22, 2023 23:34

chiragsalian requested changes May 23, 2023

View reviewed changes

src/libs/ErrorUtils.js Outdated Show resolved Hide resolved

src/libs/ErrorUtils.js Outdated Show resolved Hide resolved

src/libs/ErrorUtils.js Outdated Show resolved Hide resolved

This comment was marked as duplicate.

Sign in to view

change ErrorUtils function name and comment

35a6157

StevenKKC requested a review from chiragsalian May 23, 2023 18:51

chiragsalian requested changes May 23, 2023

View reviewed changes

fix missed error message

e4e3ea5

StevenKKC requested a review from chiragsalian May 23, 2023 19:34

chiragsalian approved these changes May 23, 2023

View reviewed changes

chiragsalian merged commit 8da2827 into Expensify:main May 23, 2023

OSBotify mentioned this pull request May 25, 2023

Deploy Checklist: New Expensify 2023-05-25 #19565

Closed

53 tasks

mvtglobally mentioned this pull request May 26, 2023

[$1000] Desktop - error message should show in Spanish #19651

Closed

6 tasks

This was referenced Jun 2, 2023

[Fix] Translated error messages #20093

Merged

[Refactor] Form validation translated error #20228

Merged

stitesExpensify mentioned this pull request Jun 8, 2023

[HOLD for payment 2023-06-23] [$1000] Return the error key rather than the translated string in all forms #20472

Closed

6 tasks

	* Return translated message for phrase.
	* Return translated string for given error

	function translateIfPhraseKey(phrase) {
	try {
	return translateLocal(phrase);
	} catch (error) {
	return phrase;
	}
	}

fix: show error message depend on the language preference #19324

fix: show error message depend on the language preference #19324

Conversation

StevenKKC commented May 19, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

github-actions bot commented May 19, 2023 • edited Loading

melvin-bot bot commented May 19, 2023

fedirjh left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

luacmartins Jun 2, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

StevenKKC commented May 20, 2023

fedirjh commented May 20, 2023

StevenKKC commented May 20, 2023

fedirjh commented May 21, 2023 • edited Loading

fedirjh commented May 21, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

fedirjh commented May 21, 2023

StevenKKC commented May 22, 2023

fedirjh left a comment

Choose a reason for hiding this comment

StevenKKC commented May 22, 2023

StevenKKC commented May 22, 2023

StevenKKC commented May 22, 2023

StevenKKC commented May 23, 2023

StevenKKC commented May 23, 2023

chiragsalian left a comment

Choose a reason for hiding this comment

This comment was marked as duplicate.

StevenKKC commented May 23, 2023

chiragsalian left a comment

Choose a reason for hiding this comment

fedirjh commented May 23, 2023 • edited Loading

StevenKKC commented May 23, 2023

StevenKKC commented May 23, 2023

chiragsalian left a comment

Choose a reason for hiding this comment

chiragsalian commented May 23, 2023 • edited Loading

OSBotify commented May 23, 2023

OSBotify commented May 25, 2023

OSBotify commented May 25, 2023

OSBotify commented May 25, 2023

OSBotify commented May 26, 2023

StevenKKC commented May 26, 2023 • edited Loading

fedirjh commented May 26, 2023 • edited Loading

StevenKKC commented May 19, 2023 •

edited

Loading

github-actions bot commented May 19, 2023 •

edited

Loading

fedirjh left a comment •

edited

Loading

luacmartins Jun 2, 2023 •

edited

Loading

fedirjh commented May 21, 2023 •

edited

Loading

fedirjh commented May 21, 2023 •

edited

Loading

fedirjh commented May 23, 2023 •

edited

Loading

chiragsalian commented May 23, 2023 •

edited

Loading

StevenKKC commented May 26, 2023 •

edited

Loading

fedirjh commented May 26, 2023 •

edited

Loading