[No QA] Implement the SubScript avatar for workspace money requests #18085

tgolen · 2023-04-27T16:57:42Z

Sorry, I did a refactoring that ended up being much larger than I had intended when I moved the policy collection to be inside of ReportUtils. That's really going to speed up all those components that no longer are connected to the collection though.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/278889

Tests

Update ReportActionsList.js to set shouldShowSubscriptAvatar={true}
Open a chat with a workspace and send a message
Verify that the avatar shows with the workspace avatar as a subscript (all we're doing here is verify that the subscript avatar is displayed and it's the correct workspace avatar)

Verify that no errors appear in the JS console

Offline tests

None

QA Steps

None. This can't be QA'ed yet because there is no way to request money from a workspace at this point.

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

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

MelvinBot · 2023-04-28T18:17:17Z

@aimane-chnaif @deetergp 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]

deetergp · 2023-04-28T19:42:27Z

Code looks good and tests well on web.

aimane-chnaif · 2023-04-28T19:43:40Z

reviewing shortly

luacmartins

LGTM and tests well! Thanks for the quick work!

aimane-chnaif · 2023-05-01T05:41:38Z

All look good but 2 things to confirm:

Is it correct that subscript avatar should be member's avatar in policy expense 1:1 chat?

I think we should show tooltip when hover subscript avatar. This already works on LHN

web3.mov

luacmartins · 2023-05-01T06:12:54Z

@aimane-chnaif the subscript avatar should only show when requesting money, but that functionality is not yet available so we are hardcoding test steps. As for the tooltip, I agree that we should add it for the workspace avatar

aimane-chnaif · 2023-05-01T06:29:09Z

the subscript avatar should only show when requesting money

ok so you mean that request money won't available at all in policy expense 1:1 chat?
It seems correct from this condition:

App/src/libs/ReportUtils.js

Line 1711 in a786349

return (!isPolicyExpenseChat(report) || report.isOwnPolicyExpenseChat);

luacmartins · 2023-05-01T06:30:54Z

ok so you mean that request money won't available at all in policy expense 1:1 chat?

It will be, but the feature is not ready yet.

tgolen · 2023-05-01T14:43:47Z

Regarding the tooltip, I can add it, but we weren't using tooltip on the normal <Avatar> in that component either. So, it seems weird to use tooltips on <SubscriptAvatar> but not <Avatar>. I think we should add the tooltips to both or to neither of them, and since they didn't exist previously on <Avatar> I would probably choose to leave them off of <SubscriptAvatar> for now.

aimane-chnaif · 2023-05-01T18:24:32Z

As SubscriptAvatar already supports tooltip, it makes sense to have structure like this, removing parent Tooltip:

if shouldShowSubscriptAvatar = true

                    <SubscriptAvatar
                        mainAvatar={{source: avatarSource, type: CONST.ICON_TYPE_AVATAR}}
                        secondaryAvatar={ReportUtils.getIcons(props.report, {})[0]}
                        mainTooltip={xxx}
                        secondaryTooltip={xxx}
                    />

if false

                    <Tooltip text={actorEmail}>
                        <Avatar
                            containerStyles={[styles.actionAvatar]}
                            source={avatarSource}
                        />
                    </Tooltip>

This is how it's done in OptionRowLHN: (MultipleAvatars has Tooltip>Avatar structure)

App/src/components/LHNOptionsList/OptionRowLHN.js

Lines 140 to 165 in 9b7d6cd

    
           optionItem.shouldShowSubscript ? ( 
        
               <SubscriptAvatar 
        
                   backgroundColor={props.isFocused ? themeColors.activeComponentBG : themeColors.sidebar} 
        
                   mainAvatar={optionItem.icons[0]} 
        
                   secondaryAvatar={optionItem.icons[1]} 
        
                   mainTooltip={optionItem.ownerEmail} 
        
                   secondaryTooltip={optionItem.subtitle} 
        
                   size={props.viewMode === CONST.OPTION_MODE.COMPACT ? CONST.AVATAR_SIZE.SMALL : CONST.AVATAR_SIZE.DEFAULT} 
        
               /> 
        
           ) : ( 
        
               <MultipleAvatars 
        
                   icons={optionItem.icons} 
        
                   isFocusMode={props.viewMode === CONST.OPTION_MODE.COMPACT} 
        
                   size={props.viewMode === CONST.OPTION_MODE.COMPACT ? CONST.AVATAR_SIZE.SMALL : CONST.AVATAR_SIZE.DEFAULT} 
        
                   secondAvatarStyle={[ 
        
                       StyleUtils.getBackgroundAndBorderStyle(themeColors.sidebar), 
        
                       props.isFocused 
        
                           ? StyleUtils.getBackgroundAndBorderStyle(focusedBackgroundColor) 
        
                           : undefined, 
        
                       hovered && !props.isFocused 
        
                           ? StyleUtils.getBackgroundAndBorderStyle(hoveredBackgroundColor) 
        
                           : undefined, 
        
                   ]} 
        
                   avatarTooltips={optionItem.isPolicyExpenseChat ? [optionItem.subtitle] : avatarTooltips} 
        
               /> 
        
           )

tgolen · 2023-05-01T19:25:25Z

Right, Thanks. I'm saying, we should NOT add tooltips because we aren't displaying tooltips here in the first place.

tgolen · 2023-05-01T20:12:08Z

because we aren't displaying tooltips here in the first place.

OK, I totally missed that we ARE using tooltips now (I missed the <Tooltip> component because I only looked inside the <OfflineWithFeedback>. So, I'll add the tooltips to the subscript too

tgolen · 2023-05-01T20:16:54Z

OK, updated with tooltips:

2023-05-01_14-16-14.mp4

aimane-chnaif · 2023-05-01T21:54:32Z

src/pages/home/report/ReportActionItemSingle.js

+                        <SubscriptAvatar
+                            mainAvatar={{source: avatarSource, type: CONST.ICON_TYPE_AVATAR}}
+                            secondaryAvatar={ReportUtils.getIcons(props.report, {})[0]}
+                            mainTooltip={props.report.ownerEmail}


Suggested change

mainTooltip={props.report.ownerEmail}

mainTooltip={actorEmail}

Agree that actorEmail is more accurate here (although they might overlap often)

aimane-chnaif

Confirmed from slack discussion that current logic we have in the PR is correct.

MelvinBot · 2023-05-02T09:46:41Z

🎯 @aimane-chnaif, thanks for reviewing and testing this PR! 🎉

An E/App issue has been created to issue payment here: #18260.

aimane-chnaif · 2023-05-02T09:47:03Z

checklisting shortly

mountiny

One question from me though is that we will also have the transaction edited report action which afaik is also IOU action type, same as deleted are we fine with whose showing the subscript too? I assume yes, but just wanted to ask that.

mountiny · 2023-05-02T09:49:29Z

src/pages/home/report/ReportActionItemSingle.js

+                        <SubscriptAvatar
+                            mainAvatar={{source: avatarSource, type: CONST.ICON_TYPE_AVATAR}}
+                            secondaryAvatar={ReportUtils.getIcons(props.report, {})[0]}
+                            mainTooltip={props.report.ownerEmail}


Agree that actorEmail is more accurate here (although they might overlap often)

aimane-chnaif · 2023-05-02T10:20:52Z

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

Mobile Web - Safari

Desktop

desktop.mov

iOS

Android

luacmartins · 2023-05-02T10:22:24Z

Yes, it seems like all system messages will use this avatar. I think we should add them to this conditional once we introduce them in App.

OSBotify · 2023-05-02T10:28:48Z

✋ 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-03T00:07:38Z

🚀 Deployed to staging by https://github.com/luacmartins in version: 1.3.9-12 🚀

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

aimane-chnaif · 2023-05-07T22:35:18Z

src/pages/home/report/ReportActionItem.js

+                                                shouldShowSubscriptAvatar={this.props.shouldShowSubscriptAvatar}
+                                                report={this.props.report}


Let's make sure to pass these values in ReportTransaction to show subscript avatar on IOUDetailsModal after we implement money request in workspace chat

App/src/components/ReportTransaction.js

Lines 65 to 68 in d120f6a

<ReportActionItemSingle

action={this.props.action}

wrapperStyles={[styles.reportTransactionWrapper]}

>

cc: @tgolen @luacmartins @mountiny

@aimane-chnaif can you submit a screenshot of where you think the SubscriptAvatar should be displayed as well? Just trying to keep things consistent since a lot of these screens will be updated/removed.

I can't have correct screenshot as money request is not implement yet in workspace chat.
But this is just example:

Right now, shows console error on this page because report is required prop but not passed

Yea, I think that page will be removed since now we'll show the report in ReportScreen and render the reportActions for each of them.

OSBotify · 2023-05-09T04:07:34Z

🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.12-0 🚀

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

tgolen added 3 commits April 27, 2023 10:05

Add prop for showing subscript avatar

ec81f47

Remove policies from params

49a9203

Get workspace avatar

588ea34

tgolen self-assigned this Apr 27, 2023

tgolen added 6 commits April 28, 2023 10:31

Merge branch 'main' into tgolen-manualrequests-subscriptavatar

600b296

Refactor getIcons to remove unnecessary params

b3f10df

Pass the proper values for avatar sources

9c7d728

Revert debug code

b27b870

Fix tests and lint

eafef33

Remove console logs

39119b9

tgolen marked this pull request as ready for review April 28, 2023 18:16

tgolen requested a review from a team as a code owner April 28, 2023 18:16

tgolen changed the title ~~Implement the SubScript avatar for workspace money requests~~ [No QA] Implement the SubScript avatar for workspace money requests Apr 28, 2023

melvin-bot bot requested review from aimane-chnaif and deetergp and removed request for a team April 28, 2023 18:17

tgolen added 2 commits April 28, 2023 12:19

Re-add the default avatar because it was still used in OptionsListUtils

be9e252

Add missing JSdoc

76044d8

deetergp previously approved these changes Apr 28, 2023

View reviewed changes

luacmartins self-requested a review April 28, 2023 20:17

luacmartins previously approved these changes Apr 29, 2023

View reviewed changes

Merge branch 'main' into tgolen-manualrequests-subscriptavatar

41e56f0

tgolen added 2 commits May 1, 2023 14:13

Move tooltip inside offline with feedback

81a4316

Add tooltips

de66bd1

tgolen dismissed stale reviews from luacmartins and deetergp via de66bd1 May 1, 2023 20:16

Remove debug code

3be3c1f

luacmartins approved these changes May 1, 2023

View reviewed changes

aimane-chnaif reviewed May 1, 2023

View reviewed changes

aimane-chnaif approved these changes May 2, 2023

View reviewed changes

melvin-bot bot mentioned this pull request May 2, 2023

[Pay on May 10th] Payment issue for E/App PR#18085 #18260

Closed

mountiny approved these changes May 2, 2023

View reviewed changes

luacmartins merged commit ac3f3c4 into main May 2, 2023

luacmartins deleted the tgolen-manualrequests-subscriptavatar branch May 2, 2023 10:22

OSBotify mentioned this pull request May 2, 2023

Deploy Checklist: New Expensify 2023-05-02 #18315

Closed

marcaaron mentioned this pull request May 3, 2023

Deploy Checklist: New Expensify 2023-05-02 #18322

Closed

59 tasks

aimane-chnaif reviewed May 7, 2023

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[No QA] Implement the SubScript avatar for workspace money requests #18085

[No QA] Implement the SubScript avatar for workspace money requests #18085

tgolen commented Apr 27, 2023 •

edited

Loading

MelvinBot commented Apr 28, 2023

deetergp commented Apr 28, 2023

aimane-chnaif commented Apr 28, 2023

luacmartins left a comment

aimane-chnaif commented May 1, 2023

luacmartins commented May 1, 2023

aimane-chnaif commented May 1, 2023

luacmartins commented May 1, 2023

tgolen commented May 1, 2023

aimane-chnaif commented May 1, 2023 •

edited

Loading

tgolen commented May 1, 2023

tgolen commented May 1, 2023

tgolen commented May 1, 2023

aimane-chnaif May 1, 2023

mountiny May 2, 2023

aimane-chnaif left a comment

MelvinBot commented May 2, 2023

aimane-chnaif commented May 2, 2023

mountiny left a comment

mountiny May 2, 2023

aimane-chnaif commented May 2, 2023

luacmartins commented May 2, 2023 •

edited

Loading

OSBotify commented May 2, 2023

OSBotify commented May 3, 2023

aimane-chnaif May 7, 2023

luacmartins May 8, 2023

aimane-chnaif May 8, 2023

aimane-chnaif May 8, 2023 •

edited

Loading

luacmartins May 8, 2023

OSBotify commented May 9, 2023

	mainTooltip={props.report.ownerEmail}
	mainTooltip={actorEmail}

		shouldShowSubscriptAvatar={this.props.shouldShowSubscriptAvatar}
		report={this.props.report}

	<ReportActionItemSingle
	action={this.props.action}
	wrapperStyles={[styles.reportTransactionWrapper]}
	>

[No QA] Implement the SubScript avatar for workspace money requests #18085

[No QA] Implement the SubScript avatar for workspace money requests #18085

Conversation

tgolen commented Apr 27, 2023 • edited Loading

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

MelvinBot commented Apr 28, 2023

deetergp commented Apr 28, 2023

aimane-chnaif commented Apr 28, 2023

luacmartins left a comment

Choose a reason for hiding this comment

aimane-chnaif commented May 1, 2023

luacmartins commented May 1, 2023

aimane-chnaif commented May 1, 2023

luacmartins commented May 1, 2023

tgolen commented May 1, 2023

aimane-chnaif commented May 1, 2023 • edited Loading

tgolen commented May 1, 2023

tgolen commented May 1, 2023

tgolen commented May 1, 2023

aimane-chnaif May 1, 2023

Choose a reason for hiding this comment

mountiny May 2, 2023

Choose a reason for hiding this comment

aimane-chnaif left a comment

Choose a reason for hiding this comment

MelvinBot commented May 2, 2023

aimane-chnaif commented May 2, 2023

mountiny left a comment

Choose a reason for hiding this comment

mountiny May 2, 2023

Choose a reason for hiding this comment

aimane-chnaif commented May 2, 2023

Reviewer Checklist

Screenshots/Videos

luacmartins commented May 2, 2023 • edited Loading

OSBotify commented May 2, 2023

OSBotify commented May 3, 2023

aimane-chnaif May 7, 2023

Choose a reason for hiding this comment

luacmartins May 8, 2023

Choose a reason for hiding this comment

aimane-chnaif May 8, 2023

Choose a reason for hiding this comment

aimane-chnaif May 8, 2023 • edited Loading

Choose a reason for hiding this comment

luacmartins May 8, 2023

Choose a reason for hiding this comment

OSBotify commented May 9, 2023

tgolen commented Apr 27, 2023 •

edited

Loading

aimane-chnaif commented May 1, 2023 •

edited

Loading

luacmartins commented May 2, 2023 •

edited

Loading

aimane-chnaif May 8, 2023 •

edited

Loading