feat: use MenuItem instead of TaskSelectorLink on Task page #20145

allroundexperts · 2023-06-04T21:47:59Z

Details

This PR removes TaskSelectorLink component and replaces it with already existing MenuItem in the NewTask page.

Fixed Issues

$ #20007
PROPOSAL: #20007 (comment)

Tests

Login to the app using any account that has ability to create tasks.
Click the + icon in the LHN and select New Task option.
Enter a title and description and click next.
Select an assignee.

Verify that the Task Confirmation page has menu items which are similar to what we see on user profile page.

Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Login to the app using any account that has ability to create tasks.
Click the + icon in the LHN and select New Task option.
Enter a title and description and click next.
Select an assignee.

Verify that the Task Confirmation page has menu items which are similar to what we see on user profile page.

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

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

melvin-bot · 2023-06-04T21:48:04Z

@thienlnam @s77rt 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]

s77rt

I haven't checked off the console error checkbox because I'm encountering this error

What are the reproduction steps for this error?

There is a difference in spaces between, please fix that as well

Before	After

s77rt · 2023-06-05T12:25:18Z

src/components/MenuItem.js

+    const stylesWithoutPadding = _.isArray(props.style)
+        ? _.map(props.style, (style) => _.omit(style, ['padding', 'paddingVertical', 'paddingHorizontal']))
+        : _.omit(props.style, ['padding', 'paddingVertical', 'paddingHorizontal']);
+    const paddingStyles = _.isArray(props.style)
+        ? _.map(props.style, (style) => _.pick(style, ['padding', 'paddingVertical', 'paddingHorizontal']))
+        : _.pick(props.style, ['padding', 'paddingVertical', 'paddingHorizontal']);


Can you please get rid of this? I don't see the need for a new View (or new padding styles)

@s77rt This is needed to create the below layout:

If we remove the View and use it as it is right now, the label will just appear to the left of icon since the container is flex-row.

In this case we should just change the default style to flex column (add it below props.style) and in the new view use flex row.

Actually, It won't require a revamp. Ignore my previous comment please.

allroundexperts · 2023-06-06T11:39:41Z

I haven't checked off the console error checkbox because I'm encountering this error

What are the reproduction steps for this error?

There is a difference in spaces between, please fix that as well

Before After

Fixed the spacing issue.

I can't seem to reproduce it after merging to main. It might be that my branch was too old.

s77rt

Bugs:

The arrow should be in the middle.
The assignee display name and email styles are inverted.

Before	After

The assignee name should be in bold same as seen in IOU selector

s77rt · 2023-06-06T18:31:00Z

src/pages/tasks/NewTaskPage.js

+                        icon={assignee.icons}
+                        onPress={() => Navigation.navigate(ROUTES.NEW_TASK_ASSIGNEE)}
+                        shouldShowRightIcon
+                        style={styles.popoverMenuItem}


Suggested change

style={styles.popoverMenuItem}

Not required

allroundexperts · 2023-06-07T00:09:03Z

Bugs:

The arrow should be in the middle.

The assignee display name and email styles are inverted.

Before After

3. The assignee name should be in bold same as seen in IOU selector

Handled!

allroundexperts · 2023-06-07T10:54:18Z

@s77rt Updated screenshots and storybook.

s77rt · 2023-06-07T15:23:47Z

src/pages/tasks/NewTaskPage.js

-                    <MenuItemWithTopDescription
+                    <MenuItem


Why we are using MenuItem and not MenuItemWithTopDescription

@s77rt This is needed in order to show the title in bold. This is how it was done at other places.

Right right

src/components/MenuItem.js

Co-authored-by: Abdelhafidh Belalia <16493223+s77rt@users.noreply.github.com>

s77rt · 2023-06-07T20:27:54Z

After creating a task getting these errors:

Warning: Failed prop type: The prop title is marked as required in MenuItemWithTopDescription, but its value is undefined.
Warning: Failed prop type: The prop title is marked as required in MenuItem, but its value is undefined.

allroundexperts · 2023-06-07T20:29:39Z

After creating a task getting these errors:

Warning: Failed prop type: The prop title is marked as required in MenuItemWithTopDescription, but its value is undefined.

Warning: Failed prop type: The prop title is marked as required in MenuItem, but its value is undefined.

Hm... that's weird. I'll check this.

allroundexperts · 2023-06-07T23:04:03Z

Weirdly I'm not able to reproduce the bug now (after reverting the last commit).

Can you please make the title required again and in the NewTaskPage pass title with a fallback e.g. title={props.task.title || ''} same as done with assignee just to be safe.

Updated.

s77rt · 2023-06-07T23:40:36Z

Almost there. Found another tiny bug, the second line is in the share somewhere section is not correct.

allroundexperts · 2023-06-07T23:45:28Z

Almost there. Found another tiny bug, the second line is in the share somewhere section is not correct.

Nice catch. Handled.

s77rt · 2023-06-07T23:46:46Z

src/pages/tasks/NewTaskPage.js

@@ -153,15 +153,15 @@ const NewTaskPage = (props) => {
                    <MenuItem
                        label={assignee.displayName ? props.translate('newTaskPage.assignee') : ''}
                        title={assignee.displayName || ''}
-                        description={assignee.subtitle ? assignee.subtitle : props.translate('newTaskPage.assignee')}
+                        description={assignee.displayName ? assignee.subtitle : props.translate('newTaskPage.assignee')}


This does not make sense. Did you mean to set the description to assignee.displayName (currently it's still assignee.subtitle)

No. The check (to show description or the label) should depend on the displayName like everywhere else.

Currently the email is not shown. Can you please add that

What do you mean? Can you share a screenshot of what you're seeing?

Hm... I think this happens on staging as well. Do we want to fix this here?

yeah let's fix this here assuming it's not much trouble

@s77rt I've checked it and I think we're doing it on purpose. The subtitle is being fetched using the getChatRoomSubtitle function in the ReportUtils. Specifically, the following condition returns it:

if (!isDefaultRoom(report) && !isUserCreatedPolicyRoom(report) && !isPolicyExpenseChat(report)) { return ''; }

I'm not sure if this is really a bug and we should block this PR because of that.

This is on main already so I won't block on that.

s77rt · 2023-06-08T17:27:08Z

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

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

s77rt · 2023-06-08T17:28:10Z

One more bug to go 😅

The avatars ring should match the background color (based on hover state)

allroundexperts · 2023-06-08T19:23:08Z

One more bug to go 😅

The avatars ring should match the background color (based on hover state)

@s77rt Fixed.

s77rt · 2023-06-08T21:29:44Z

@allroundexperts Can you please also cover the case where the menu item is clicked

allroundexperts · 2023-06-08T21:59:57Z

@allroundexperts Can you please also cover the case where the menu item is clicked

@s77rt I've fixed it. But it might be worth checking with @shawnborton about the border colours of multiple avatar component for the menu item above in all three states (not hovered, hovered, pressed)

allroundexperts · 2023-06-08T22:07:05Z

Normal State
Colour for border -> #07271F

Hovered State
Colour for border -> #1A3D32

Pressed State
Colour for border -> #467164

@shawnborton Please let us know if these need changes.

shawnborton · 2023-06-09T06:18:36Z

That makes sense to me.

s77rt

LGTM! 🚀

cc @thienlnam

thienlnam · 2023-06-09T14:49:42Z

Awesome, thanks guys!

OSBotify · 2023-06-09T14:55:38Z

✋ 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-06-13T00:32:45Z

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.3.27-0 🚀

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

OSBotify · 2023-06-13T01:06:56Z

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.3.27-0 🚀

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

OSBotify · 2023-06-14T21:23:03Z

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.27-7 🚀

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

sobitneupane · 2023-07-24T15:31:53Z

src/pages/tasks/NewTaskPage.js

-                            onPress={() => Navigation.navigate(ROUTES.NEW_TASK_SHARE_DESTINATION)}
-                            label="newTaskPage.shareSomewhere"
-                            isShareDestination
-                            disabled={Boolean(props.task.parentReportID)}


This condition was not considered while making the change causing this regression.

Sorry for that. Thanks for the highlight @sobitneupane

rushatgabhane · 2023-08-02T18:00:04Z

src/pages/tasks/NewTaskPage.js

+                    <MenuItem
+                        label={assignee.displayName ? props.translate('newTaskPage.assignee') : ''}
+                        title={assignee.displayName || ''}
+                        description={assignee.displayName ? assignee.subtitle : props.translate('newTaskPage.assignee')}


Hi, this caused a bug - Phone number contact in task assignee is displayed with @expensify.sms

We should have sanitized the asignee because it can be a phone number.

@rushatgabhane Thanks for the report. Just trying to understand if this is something we missed because I think we just mapped the logic from TaskSelectorLink where the assignee was handled as is without taking phone number in consideration

App/src/components/TaskSelectorLink.js

Lines 83 to 89 in 49895f4

{props.alternateText ? (

<Text

style={alternateTextStyle}

numberOfLines={1}

>

{props.alternateText}

</Text>

sobitneupane · 2023-08-31T17:04:05Z

src/components/MenuItem.js

+                                        StyleUtils.getBackgroundAndBorderStyle(themeColors.sidebar),
+                                        pressed ? StyleUtils.getBackgroundAndBorderStyle(themeColors.buttonPressedBG) : undefined,
+                                        hovered && !pressed ? StyleUtils.getBackgroundAndBorderStyle(themeColors.border) : undefined,
+                                    ]}


This regression was probably caused by the PR.

Issue: Task - Second avatar of group avatar is highlighted when long pressing on Share somewhere

feat: use MenuItem instead of TaskSelectorLink on Task page

abb3861

allroundexperts requested a review from a team as a code owner June 4, 2023 21:47

melvin-bot bot requested review from s77rt and thienlnam and removed request for a team June 4, 2023 21:48

allroundexperts mentioned this pull request Jun 4, 2023

[HOLD for payment 2023-06-21] [$1000] Inconsistent styling on create task push to page #20007

Closed

Skalakid mentioned this pull request Jun 5, 2023

[Accessable Pressables] Migrate TaskSelectorLink to use new Pressables #20020

Closed

fix: prettier errors

fe9ba8d

s77rt suggested changes Jun 5, 2023

View reviewed changes

allroundexperts added 2 commits June 6, 2023 15:53

merge with main and resolve conflicts

dc7f9a5

fix: removed extra space between task menu items

8290ff1

allroundexperts requested a review from s77rt June 6, 2023 11:39

s77rt suggested changes Jun 6, 2023

View reviewed changes

fix: vertically center the menu item right icons

5f0a6ff

allroundexperts requested a review from s77rt June 7, 2023 00:09

allroundexperts added 2 commits June 7, 2023 05:12

fix: make menu item container take up full height

7fd48bc

fix: add storybook item for the updated menuitem

58a13b3

s77rt reviewed Jun 7, 2023

View reviewed changes

fix: lint errors

3602dfc

allroundexperts requested a review from s77rt June 7, 2023 19:19

s77rt suggested changes Jun 7, 2023

View reviewed changes

src/components/MenuItem.js Outdated Show resolved Hide resolved

Update src/components/MenuItem.js

26e14c5

Co-authored-by: Abdelhafidh Belalia <16493223+s77rt@users.noreply.github.com>

allroundexperts added 2 commits June 8, 2023 02:34

Merge branch 'main' into fix-20007

6dffed9

fix: make title optional in menu item

a492529

fix: incorrect task page menu item description

6518b02

s77rt reviewed Jun 7, 2023

View reviewed changes

fix: use correct border for MultipleAvatar inside MenuItem

553b3c6

fix: prettier errors

1310ded

fix: add press colour for menu item avatars

d4e51ec

s77rt approved these changes Jun 9, 2023

View reviewed changes

thienlnam approved these changes Jun 9, 2023

View reviewed changes

thienlnam merged commit 68d154d into Expensify:main Jun 9, 2023

OSBotify mentioned this pull request Jun 12, 2023

Deploy Checklist: New Expensify 2023-06-12 #20640

Closed

71 tasks

sobitneupane reviewed Jul 24, 2023

View reviewed changes

sobitneupane mentioned this pull request Jul 24, 2023

[HOLD for payment 2023-07-21] [$1000] Share somewhere doesn't update in room while selecting user/group #21614

Closed

6 tasks

rushatgabhane reviewed Aug 2, 2023

View reviewed changes

rushatgabhane mentioned this pull request Aug 2, 2023

[Awaiting C+ payment] [HOLD for payment 2023-07-24] [$1000] Phone number contact in task assignee is displayed with @expensify.sms #22050

Closed

6 tasks

sobitneupane reviewed Aug 31, 2023

View reviewed changes

sobitneupane mentioned this pull request Aug 31, 2023

[HOLD for payment 2023-08-24] [$1000] Task - Second avatar of group avatar is highlighted when long pressing on Share somewhere #24008

Closed

6 tasks

	{props.alternateText ? (
	<Text
	style={alternateTextStyle}
	numberOfLines={1}
	>
	{props.alternateText}
	</Text>

feat: use MenuItem instead of TaskSelectorLink on Task page #20145

feat: use MenuItem instead of TaskSelectorLink on Task page #20145

Conversation

allroundexperts commented Jun 4, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jun 4, 2023

s77rt left a 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

This comment was marked as outdated.

Choose a reason for hiding this comment

allroundexperts commented Jun 6, 2023

s77rt left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

allroundexperts commented Jun 7, 2023

allroundexperts commented Jun 7, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

s77rt commented Jun 7, 2023

allroundexperts commented Jun 7, 2023

allroundexperts commented Jun 7, 2023

s77rt commented Jun 7, 2023

allroundexperts commented Jun 7, 2023

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

Choose a reason for hiding this comment

Choose a reason for hiding this comment

s77rt commented Jun 8, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

s77rt commented Jun 8, 2023

allroundexperts commented Jun 8, 2023

s77rt commented Jun 8, 2023

allroundexperts commented Jun 8, 2023

allroundexperts commented Jun 8, 2023 • edited Loading

shawnborton commented Jun 9, 2023

s77rt left a comment

Choose a reason for hiding this comment

thienlnam commented Jun 9, 2023

OSBotify commented Jun 9, 2023

OSBotify commented Jun 13, 2023

OSBotify commented Jun 13, 2023

OSBotify commented Jun 14, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rushatgabhane Aug 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

allroundexperts commented Jun 4, 2023 •

edited

Loading

s77rt commented Jun 8, 2023 •

edited

Loading

allroundexperts commented Jun 8, 2023 •

edited

Loading

rushatgabhane Aug 2, 2023 •

edited

Loading