Followup #23961: update IOU report total in optimistic data on edit money request by BeeMargarida · Pull Request #25498 · Expensify/App

BeeMargarida · 2023-08-18T15:19:28Z

Details

Updates the optimistic data of the IOU report when a money request is edited. It only updates it if the currency matches and the amount was changed.

Fixed Issues

$ #23961

Tests

Open a money request
Go offline
Edit the amount
Check that the total amount updates

Verify that no errors appear in the JS console

Offline tests

Open a money request
Go offline
Edit the amount
Check that the total amount updates

QA Steps

Open a money request
Go offline
Edit the amount
Check that the total amount updates

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
- If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
- 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 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 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_t.mp4

Mobile Web - Chrome

mchrome_t.mp4

Mobile Web - Safari

msafari_t.mp4

Desktop

desktop_t.mp4

iOS

ios_t.mp4

Android

android_t.mp4

melvin-bot · 2023-08-21T10:57:00Z

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

allroundexperts · 2023-08-21T11:20:05Z

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

screen-recording-2023-08-28-at-24350-pm_Ci0fDSzK.mp4

screen-recording-2023-08-28-at-24600-pm_W0q2mj8b.mp4

Mobile Web - Chrome

Screen.Recording.2023-08-28.at.2.54.02.PM.mov

Mobile Web - Safari

Screen.Recording.2023-08-28.at.3.03.01.PM.mov

Desktop

Screen.Recording.2023-08-28.at.2.49.42.PM.mov

iOS

Screen.Recording.2023-08-28.at.3.01.21.PM.mov

Android

Screen.Recording.2023-08-28.at.3.20.27.PM.mov

allroundexperts · 2023-08-21T15:51:28Z

Hi @BeeMargarida!
The amount on the LHN isn't changing.

Screen.Recording.2023-08-21.at.8.45.20.PM.mov

…ter_edit

BeeMargarida · 2023-08-21T16:20:45Z

@allroundexperts Hum, it seems to be working on my side. Are you using the same currency as the one in the report, right?

(I merged with main, I was having some issues with logging in)

asd_t.mp4

allroundexperts · 2023-08-21T19:15:24Z

I was using the same currency as in report. I will try again!

allroundexperts · 2023-08-21T20:20:33Z

Still happening for me @BeeMargarida. @mountiny Can you maybe confirm this please?

Screen.Recording.2023-08-22.at.1.18.38.AM.mov

mountiny · 2023-08-21T21:48:16Z

For me its partial. The IOU report updates, the report title of the request is still the old 30 instead of 40 and the report preview total is incorrect. Could we look into updating that too? @BeeMargarida

allroundexperts · 2023-08-21T21:49:05Z

It's the same for me. The title in the LHN never updates.

mountiny · 2023-08-22T11:03:24Z

@BeeMargarida Lets make sure to circle back to this one today 🙇

BeeMargarida · 2023-08-22T13:57:21Z

Working on this still, it's more tricky than I though. Fixed the previews, just missing the update to the request title

mountiny · 2023-08-22T15:33:59Z

thanks for the update

BeeMargarida · 2023-08-23T09:00:53Z

@allroundexperts @mountiny Should be fixed now

change_t.mp4

mountiny · 2023-08-23T15:28:39Z

@allroundexperts any chance you can get to this today?

allroundexperts · 2023-08-23T15:29:42Z

@mountiny I'll look at all the outstanding PRs after 3 hours.

allroundexperts · 2023-08-23T22:46:35Z

+    const transactionID = lodashGet(parentReportAction, ['originalMessage', 'IOUTransactionID'], '');
+    const transaction = lodashGet(transactions, [`${ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}`], '');


You can also just load this single transaction by composing multiple withOnyx.

This will cause a lot of re-renders since we're including all the transactions. Similar optimisation can also be done for the parentReportAction above

You mean having several withOnyx that depend on one another? Won't those also be injected as props? Or we ignore the transactions prop and only use the one transaction?

I don't think this is possible, because there's no way to access the parentReportAction by key. And this parentReportAction is necessary to access the transaction. So we can't do this in withOnyx.
Or am I missing something? 🤔

The only thing that I think would work is make a withReportActions where we could pass transformValue that selected the report action taking into account the fullreport.

I think you can use selector function from onyx. No?

I don't think so, because in the selector we don't have access to the props, so we couldn't use the fullReport to access the correct report action

Hm...
Can't you add the following here:

withOnyx({ transaction: { key: ({parentReportActions, fullReport}) => `${ONYXKEYS.COLLECTION.TRANSACTION}${lodashGet(parentReportActions[fullReport.parentReportActionID], ['originalMessage', 'IOUTransactionID'], '')}`, canEvict: false, }, }),

Yap, I think I can do that, but I can't make the same refactor to parentReportActions.
Well, I can, but I need to make a withReportActions HOC (allows to use the props in transformValue so we can only get the report action that we want). I've developed this and it seems to work fine. Do you think this optimization is worth it?
Note: the optimization could also be applied to the policies prop.

If you're the owner of this code, and you think its not worth it, then I'm totally fine with this as well!

@mountiny Do you agree?

BeeMargarida · 2023-08-24T09:56:54Z

@allroundexperts @mountiny Updated! As mentioned above, I've not optimized the parentReportActions, but I have the HOC code, in case we end up going that way. For now, only the transaction and policy were optimized in OptionRowLHNData

allroundexperts

This is working well. However, @mountiny the description is not getting updated optimistically. Do we have an issue to keep track of this?

Also, editing a request which resulted from a split bill request originally, does not reflect in the actual split bill report. Not sure if we are tracking this either.

mountiny · 2023-09-12T02:11:42Z

Also, editing a request which resulted from a split bill request originally, does not reflect in the actual split bill report. Not sure if we are tracking this either.

This is out of scope

This is working well. However, @mountiny the description is not getting updated optimistically. Do we have an issue to keep track of this?

What do you mean exactly?

allroundexperts · 2023-09-12T09:32:26Z

What do you mean exactly?

When you update the description (while offline), the updated description does not show up in the top bar until you refresh the page.

mountiny · 2023-09-12T10:19:44Z

Oh I get waht you mean now and I am not sure if there is an issue for that. I think we could actually just fix it in this PR? @BeeMargarida would you be available to address this. Update the description in the header optimistically too when its changed. In the screenshot its the for test

BeeMargarida · 2023-09-12T10:21:05Z

@mountiny @allroundexperts Hum, weird, I'm positive this was working before 🤔 I'll check it out

BeeMargarida · 2023-09-12T11:44:50Z

@mountiny @allroundexperts Should be working now 👍

vid_t.mp4

allroundexperts · 2023-09-12T23:09:30Z

Getting this console error @BeeMargarida.

Otherwise, this is working well.

Screen.Recording.2023-09-13.at.4.04.12.AM.mov

BeeMargarida · 2023-09-13T08:14:07Z

@allroundexperts Should be fixed now

mountiny · 2023-09-13T09:17:16Z

@allroundexperts can you please double check?

allroundexperts · 2023-09-14T01:14:51Z

Working well now!

Screen.Recording.2023-09-14.at.6.12.31.AM.mov

mountiny

One question

BeeMargarida · 2023-09-14T10:04:40Z

@mountiny Updated!

mountiny

Thanks for the patience here!

OSBotify · 2023-09-14T10:51:58Z

🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.70-0 🚀

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

mountiny · 2023-09-14T14:44:04Z

+    // from the server with the currency conversion
+    let updatedMoneyRequestReport = {...iouReport};
+    const updatedChatReport = {...chatReport};
+    if (updatedTransaction.currency === iouReport.currency && updatedTransaction.modifiedAmount) {


@BeeMargarida @rezkiy37 run into an issue because the modifiedAmount is true after oneamount update, the modified amount is always there, I think we have to look at the amount diff here, are you able to make a follow up PR?

Yes, I'll make a PR with that fix

The regression fix PR: #27451 (comment)

OSBotify · 2023-09-18T10:09:57Z

🚀 Deployed to production by https://github.com/thienlnam in version: 1.3.70-8 🚀

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

aimane-chnaif · 2023-10-04T07:50:17Z

+            onyxMethod: Onyx.METHOD.MERGE,
+            key: `${ONYXKEYS.COLLECTION.REPORT}${iouReport.chatReportID}`,
+            value: updatedChatReport,
+        },


We should have set lastReadTime and lastVisibleActionCreated of transaction thread report in optimistic data.
Without this, unread indicator didn't show even after marking report action as unread after changing date offline.
Issue: #27159

Beamanator · 2023-10-23T13:21:50Z

+
+        // Update the last message of the chat report
+        const messageText = Localize.translateLocal('iou.payerOwesAmount', {
+            payer: updatedMoneyRequestReport.managerEmail,


How hard would it be to update this to use updatedMoneyRequestReport.managerID instead?

We're trying to get rid of all uses of managerEmail 🙏

I guess not that hard just time consuming as we need to make prs across stack from back to front end and back, do you have an issue specifically for these flows?

This may be the most related one: https://github.com/Expensify/Expensify/issues/294647

feat: update IOU report total in optimistic data on edit money request

f0ff0a7

BeeMargarida marked this pull request as ready for review August 21, 2023 10:56

BeeMargarida requested a review from a team as a code owner August 21, 2023 10:56

melvin-bot Bot requested review from allroundexperts and removed request for a team August 21, 2023 10:56

Merge branch 'main' into ms/23961-optimistic_data_iou_total_update_af…

72784d4

…ter_edit

mountiny assigned BeeMargarida Aug 21, 2023

BeeMargarida added 2 commits August 22, 2023 15:00

feat: change message values of report when IOU amount changes

b7dc724

fix: typo

7c9706e

fix: re-render when transaction for LHN changes

c7a2d06

allroundexperts suggested changes Aug 23, 2023

View reviewed changes

mountiny reviewed Aug 23, 2023

View reviewed changes

Comment thread src/libs/actions/IOU.js Outdated

Comment thread src/libs/actions/IOU.js

Comment thread src/libs/actions/IOU.js Outdated

Comment thread src/libs/actions/IOU.js Outdated

Comment thread src/libs/actions/IOU.js Outdated

BeeMargarida added 3 commits August 24, 2023 09:48

fix: simplify total calculation and add missing proptype

4cbd6d5

fix: small fix

db3cf8a

feat: improve prop composition

ea2926f

mountiny changed the title ~~[hold merge freeze] Followup #23961: update IOU report total in optimistic data on edit money request~~ Followup #23961: update IOU report total in optimistic data on edit money request Sep 11, 2023

allroundexperts approved these changes Sep 11, 2023

View reviewed changes

fix: update header when description changes

529180d

fix: console error

2590bdc

allroundexperts approved these changes Sep 14, 2023

View reviewed changes

mountiny previously approved these changes Sep 14, 2023

View reviewed changes

Comment thread src/components/MoneyRequestHeader.js Outdated

fix: do not use onyx subscription composition

58346d1

BeeMargarida dismissed mountiny’s stale review via 58346d1 September 14, 2023 09:53

mountiny approved these changes Sep 14, 2023

View reviewed changes

mountiny merged commit 1a49026 into Expensify:main Sep 14, 2023

OSBotify mentioned this pull request Sep 14, 2023

Deploy Checklist: New Expensify 2023-09-14 #27425

Closed

mountiny reviewed Sep 14, 2023

View reviewed changes

aimane-chnaif mentioned this pull request Sep 15, 2023

Remove data from being sideloaded in the money request header #27286

Merged

59 tasks

im-adithya mentioned this pull request Sep 17, 2023

fix: re-calculate totals when invoice is edited #26486

Closed

59 tasks

mananjadhav mentioned this pull request Sep 17, 2023

[$500] IOU - Incorrect total amount shown when deleting money request in offline mode #26054

Closed

6 tasks

aimane-chnaif reviewed Oct 4, 2023

View reviewed changes

aimane-chnaif mentioned this pull request Oct 4, 2023

[WAITING ON AIMANE TO COMPLETE CHECKLIST] [HOLD for payment 2023-10-02] [$500] Request money - Unread indicator doesn't appear when marking as unread in offline #27159

Closed

6 tasks

Beamanator reviewed Oct 23, 2023

View reviewed changes

		const transactionID = lodashGet(parentReportAction, ['originalMessage', 'IOUTransactionID'], '');
		const transaction = lodashGet(transactions, [`${ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}`], '');

Uh oh!

Conversation

BeeMargarida commented Aug 18, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented Aug 21, 2023

Uh oh!

allroundexperts commented Aug 21, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

allroundexperts commented Aug 21, 2023

Uh oh!

BeeMargarida commented Aug 21, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

allroundexperts commented Aug 21, 2023

Uh oh!

allroundexperts commented Aug 21, 2023

Uh oh!

mountiny commented Aug 21, 2023

Uh oh!

allroundexperts commented Aug 21, 2023

Uh oh!

mountiny commented Aug 22, 2023

Uh oh!

BeeMargarida commented Aug 22, 2023

Uh oh!

mountiny commented Aug 22, 2023

Uh oh!

BeeMargarida commented Aug 23, 2023

Uh oh!

mountiny commented Aug 23, 2023

Uh oh!

allroundexperts commented Aug 23, 2023

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

BeeMargarida Aug 24, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

BeeMargarida Aug 24, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

BeeMargarida Aug 24, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

allroundexperts Aug 24, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

BeeMargarida commented Aug 24, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

BeeMargarida commented Aug 18, 2023 •

edited

Loading

allroundexperts commented Aug 21, 2023 •

edited

Loading

BeeMargarida commented Aug 21, 2023 •

edited

Loading

BeeMargarida Aug 24, 2023 •

edited

Loading

BeeMargarida Aug 24, 2023 •

edited

Loading

BeeMargarida Aug 24, 2023 •

edited

Loading

allroundexperts Aug 24, 2023 •

edited

Loading

BeeMargarida commented Aug 24, 2023 •

edited

Loading

BeeMargarida commented Sep 12, 2023 •

edited

Loading