feat: Build optimistic Edit Task actions #36768

paultsimura · 2024-02-17T22:26:21Z

Details

Fixed Issues

$ #36196
PROPOSAL: #36196 (comment)

Tests

Same as QA

Offline tests

Same as QA

QA Steps

Create a task
Go offline
Add a description
Verify the updated the description to {value} report action is added
Modify the title
Verify another updated the task title to {value} report action is added
Remove the description
Verify the removed the description report action is added
Assign somebody
Verify the assigned to @user report action is added
Go online
Refresh the page
Verify all the report actions remain

PR Author Checklist

Screenshots/Videos

Android: Native

android-compressed.mp4

Android: mWeb Chrome

chrome-compressed.mp4

iOS: Native

Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-02-29.at.18.24.41-compressed.mp4

iOS: mWeb Safari

Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-02-29.at.18.28.26-compressed.mp4

MacOS: Chrome / Safari

Screen.Recording.2024-02-29.at.02.03.51-compressed.mp4

MacOS: Desktop

Screen.Recording.2024-02-29.at.17.48.23-compressed.mp4

paultsimura · 2024-02-19T08:43:28Z

@thienlnam there are some points I'd like to discuss with you.

First of all, the EditTaskAssignee and EditTask API calls do not return the "modified" reportAction in the response – it comes later from the OpenReport, so we need to refresh (or revisit) the report page to replace the optimistic report action with the one from the server – this should be fixed on the BE side.

The second is related to the mentions when changing the assignee. Currently, they come from the BE in this format:

[
  {
    "type": "TEXT",
    "style": "normal",
    "text": "assigned to <mention-user>user_d (paultsimura+d@gmail.com)</mention-user>"
  }
]

This is incorrect in a couple of ways. First, the <mention-user> tag doesn't support this format – the easiest way would be to use the accountId param, e.g.:

`assigned to <mention-user accountID=${assigneeAccountID}></mention-user>`

The display name will be fetched automatically by the provided accountID by the HTML renderer.

And one last thing is the "type": "TEXT" doesn't support the HTML render – it will show the action as a plain text. We need to use the "type": "COMMENT" in order for mentions to be displayed correctly, or think of a way to allow parsing HTML in the TEXT actions.

thienlnam · 2024-02-20T21:56:21Z

Thanks for the comments

First of all, the EditTaskAssignee and EditTask API calls do not return the "modified" reportAction in the response – it comes later from the OpenReport, so we need to refresh (or revisit) the report page to replace the optimistic report action with the one from the server – this should be fixed on the BE side.

Which reportAction are you referring to in this case? There should be a pusher update which updates the parent reportAction data so you don't need to fetch it from the API call. Though if you're talking about the edited reportAction, I agree we might need to update it so that it does

As for the other items, I'll get a fix up for those!

paultsimura · 2024-02-20T22:09:23Z

Though if you're talking about the edited reportAction

Yes, I'm talking about them. The optimistic ones do not get replaced with the ones from BE until the page is refreshed, we just need to add one more merge to the BE response.

paultsimura · 2024-02-20T22:16:55Z

As for the other items, I'll get a fix up for those!

Would be great if you could test this PR's optimistic flow to see if the BE should match it – so that we'll be on the same page.

As a side note: I saw you intended to use the Assigned to "you" mention format from the BE – I'm not sure it's something we currently support – the self-mention will render also with the displayName, but highlighted in green (all other mentions will be blue).

thienlnam · 2024-02-20T22:26:49Z

As a side note: I saw you intended to use the Assigned to "you" mention format from the BE – I'm not sure it's something we currently support – the self-mention will render also with the displayName, but highlighted in green (all other mentions will be blue).

The "you" wasn't going to be a mention, but I think I'll just update it to be a mention and then it will show as green - that's okay as well

paultsimura · 2024-02-20T23:19:45Z

The "you" wasn't going to be a mention

It's currently coming from BE like this, therefore I assumed the mention 🙂

thienlnam · 2024-02-21T02:10:26Z

I tested the changes with your branch, looks good - seems like the only change that is needed is for the comments to show as system messages UI

paultsimura · 2024-02-21T05:40:23Z

We have at least 2 formats of system messages. Do you mean we would like the TASKEDITED messages to look like the "room renamed" actions (the second screenshot), not like the "Paid" ones (first screenshot)?

If so – we'll need to change the action format a little, so I'll ask you to hold on with the BE change for a while.

thienlnam · 2024-02-21T17:40:33Z

No no, they should look like the first screenshot - I more meant that it the UI should be in the same text color from this screenshot #36768 (comment)

Though, I don't think I've seen a mention within a system message so this might be new

paultsimura · 2024-02-21T17:45:57Z

Ah yes - that's a bit of an issue — the bold system-like formatting is supported by the actions of type TEXT, but these actions do not support mentions. And vice-versa, the COMMENT type supports mentions, but not the formatting. I can look what we can do with this formatting, but need to know if it's worth the time at this point

thienlnam · 2024-02-21T18:02:48Z

Hahah of course there is something like that - I think for now it's okay to keep as is so no need to spend additional time investigating. Thanks for being willing though

paultsimura · 2024-02-21T20:54:39Z

Great, so I'm waiting for your BE changes before moving this PR to review, right?

thienlnam · 2024-02-21T21:31:28Z

Yes that's correct - the PRs are in review currently. I'll let you know when they're on production

thienlnam · 2024-02-27T20:04:21Z

Changes should be on production now

paultsimura · 2024-02-28T14:51:19Z

Thanks @thienlnam. They are, so I'm unblocked now, but this one's still missing: #36768 (comment)

The EditTask API response does not update the task report's reportActions to include the new TASKEDITED action.
Here's the recording, the reportActions is updated with the server data only after we refresh the page and the OpenReport response comes (the task report ID is 5598782205931668):

Screen.Recording.2024-02-28.at.15.47.16-compressed.mp4

We must add them, otherwise, it's messing with the order of the action when coming online having a couple of actions pending (I suppose this is the root cause):

Untitled-compressed.mp4

paultsimura · 2024-02-28T22:48:29Z

@thienlnam another BE bug: when editing the assignee, we need to add their display name to the reportAction.message.text.

This is what an optimistic action looks like (note the text in LHN as a result):

And here's what it becomes after coming online and being updated from the BE:

paultsimura · 2024-02-28T23:19:46Z

One more thing @thienlnam, sorry.

In money requests, we don't count the MODIFIEDEXPENSE system messages as visibleChildReportActions, therefore a money request with only such messages can be fully deleted (if there are other messages inside – the report won't be deleted). Also, these messages are not counted as "thread replies count".
Demo:

Screen.Recording.2024-02-29.at.00.17.48-compressed.mp4

Do I understand correctly that we want to implement a similar approach for tasks?

thienlnam · 2024-02-29T01:35:00Z

No worries, thanks for pointing these out - the second one has been an issue and I'll address those issues likely next week but it shouldn't block this PR from going out

Do I understand correctly that we want to implement a similar approach for tasks?

Yes, we want the task to delete entirely if there are no other visible reportActions - however, instead of changing it so that it doesn't count as a visible reportAction (because it is actually visible). Though I'd need to double check if this is a pattern we're taking with all system messages or not. Ideally I think we would just check that there are no visible reportActions or only system messages

Also, these messages are not counted as "thread replies count".

I'll add this to the list of BE fixes needed

paultsimura · 2024-02-29T01:43:25Z

Also, these messages are not counted as "thread replies count".

I'll add this to the list of BE fixes needed

This is similar to how it's done with the Money Request system messages as well as the "task completed/reopened", so I would double-check that - it seems expected to me.

This PR is ready for review code-wise, so I would recommend just checking how the branch works, and letting me know if something is misaligned with your vision.
Btw, I managed to make these messages look like the system ones.

paultsimura · 2024-03-04T23:08:10Z

Bug:

Create a task

Go offline

Add a description

Add an assignee

Mark as complete

Mark as incomplete

At this point all of the report actions are in the correct order

Go online

Notice "marked as complete" and "marked as incomplete" items changing position while the app refreshes

That's known: #36768 (comment)

@thienlnam is tracking this on the BE side.

paultsimura · 2024-03-04T23:32:41Z

I think we should localize the actions, they aren't translated into Spanish

For this, we'll need another BE change.
@thienlnam could you please add to your tracking issue the following?

The TASKEDITED report actions should reflect the MODIFIEDEXPENSE:

The API endpoint must consume one field at a time (title / description);
The originalMessage must contain only the changed field (old + new value), as it is for expenses:

Updated Description:

{
  "oldComment": "",
  "newComment": "Desc",
  "lastModified": "2024-03-04 23:22:47.451"
}

Updated Merchant:

{
  "oldMerchant": "Old Merchant",
  "merchant": "New Merchant",
  "lastModified": "2024-03-04 23:28:22.705"
}

We need to make sure the originalMessage will cover the title, description, and assigneeAccountID change.
Based on this, we'll be able to build a localizable message for each TASKEDITED action, similar to MODIFIEDEXPENSE here:

App/src/libs/ModifiedExpenseMessage.ts

Lines 100 to 239 in 5609744

    
           function getForReportAction(reportID: string | undefined, reportAction: OnyxEntry<ReportAction>): string { 
        
               if (reportAction?.actionName !== CONST.REPORT.ACTIONS.TYPE.MODIFIEDEXPENSE) { 
        
                   return ''; 
        
               } 
        
               const reportActionOriginalMessage = reportAction?.originalMessage as ExpenseOriginalMessage | undefined; 
        
               const policyID = ReportUtils.getReportPolicyID(reportID) ?? ''; 
        
               const removalFragments: string[] = []; 
        
               const setFragments: string[] = []; 
        
               const changeFragments: string[] = []; 
        
               const hasModifiedAmount = 
        
                   reportActionOriginalMessage && 
        
                   'oldAmount' in reportActionOriginalMessage && 
        
                   'oldCurrency' in reportActionOriginalMessage && 
        
                   'amount' in reportActionOriginalMessage && 
        
                   'currency' in reportActionOriginalMessage; 
        
               const hasModifiedMerchant = reportActionOriginalMessage && 'oldMerchant' in reportActionOriginalMessage && 'merchant' in reportActionOriginalMessage; 
        
               if (hasModifiedAmount) { 
        
                   const oldCurrency = reportActionOriginalMessage?.oldCurrency ?? ''; 
        
                   const oldAmountValue = reportActionOriginalMessage?.oldAmount ?? 0; 
        
                   const oldAmount = oldAmountValue > 0 ? CurrencyUtils.convertToDisplayString(reportActionOriginalMessage?.oldAmount ?? 0, oldCurrency) : ''; 
        
                   const currency = reportActionOriginalMessage?.currency ?? ''; 
        
                   const amount = CurrencyUtils.convertToDisplayString(reportActionOriginalMessage?.amount ?? 0, currency); 
        
                   // Only Distance edits should modify amount and merchant (which stores distance) in a single transaction. 
        
                   // We check the merchant is in distance format (includes @) as a sanity check 
        
                   if (hasModifiedMerchant && (reportActionOriginalMessage?.merchant ?? '').includes('@')) { 
        
                       return getForDistanceRequest(reportActionOriginalMessage?.merchant ?? '', reportActionOriginalMessage?.oldMerchant ?? '', amount, oldAmount); 
        
                   } 
        
                   buildMessageFragmentForValue(amount, oldAmount, Localize.translateLocal('iou.amount'), false, setFragments, removalFragments, changeFragments); 
        
               } 
        
               const hasModifiedComment = reportActionOriginalMessage && 'oldComment' in reportActionOriginalMessage && 'newComment' in reportActionOriginalMessage; 
        
               if (hasModifiedComment) { 
        
                   buildMessageFragmentForValue( 
        
                       reportActionOriginalMessage?.newComment ?? '', 
        
                       reportActionOriginalMessage?.oldComment ?? '', 
        
                       Localize.translateLocal('common.description'), 
        
                       true, 
        
                       setFragments, 
        
                       removalFragments, 
        
                       changeFragments, 
        
                   ); 
        
               } 
        
               if (reportActionOriginalMessage?.oldCreated && reportActionOriginalMessage?.created) { 
        
                   const formattedOldCreated = DateUtils.formatWithUTCTimeZone(reportActionOriginalMessage.oldCreated, CONST.DATE.FNS_FORMAT_STRING); 
        
                   buildMessageFragmentForValue( 
        
                       reportActionOriginalMessage.created, 
        
                       formattedOldCreated, 
        
                       Localize.translateLocal('common.date'), 
        
                       false, 
        
                       setFragments, 
        
                       removalFragments, 
        
                       changeFragments, 
        
                   ); 
        
               } 
        
               if (hasModifiedMerchant) { 
        
                   buildMessageFragmentForValue( 
        
                       reportActionOriginalMessage?.merchant ?? '', 
        
                       reportActionOriginalMessage?.oldMerchant ?? '', 
        
                       Localize.translateLocal('common.merchant'), 
        
                       true, 
        
                       setFragments, 
        
                       removalFragments, 
        
                       changeFragments, 
        
                   ); 
        
               } 
        
               const hasModifiedCategory = reportActionOriginalMessage && 'oldCategory' in reportActionOriginalMessage && 'category' in reportActionOriginalMessage; 
        
               if (hasModifiedCategory) { 
        
                   buildMessageFragmentForValue( 
        
                       reportActionOriginalMessage?.category ?? '', 
        
                       reportActionOriginalMessage?.oldCategory ?? '', 
        
                       Localize.translateLocal('common.category'), 
        
                       true, 
        
                       setFragments, 
        
                       removalFragments, 
        
                       changeFragments, 
        
                   ); 
        
               } 
        
               const hasModifiedTag = reportActionOriginalMessage && 'oldTag' in reportActionOriginalMessage && 'tag' in reportActionOriginalMessage; 
        
               if (hasModifiedTag) { 
        
                   const policyTags = allPolicyTags?.[`${ONYXKEYS.COLLECTION.POLICY_TAGS}${policyID}`] ?? {}; 
        
                   const transactionTag = reportActionOriginalMessage?.tag ?? ''; 
        
                   const oldTransactionTag = reportActionOriginalMessage?.oldTag ?? ''; 
        
                   const splittedTag = TransactionUtils.getTagArrayFromName(transactionTag); 
        
                   const splittedOldTag = TransactionUtils.getTagArrayFromName(oldTransactionTag); 
        
                   const localizedTagListName = Localize.translateLocal('common.tag'); 
        
                   Object.keys(policyTags).forEach((policyTagKey, index) => { 
        
                       const policyTagListName = PolicyUtils.getTagListName(policyTags, index) || localizedTagListName; 
        
                       const newTag = splittedTag[index] ?? ''; 
        
                       const oldTag = splittedOldTag[index] ?? ''; 
        
                       if (newTag !== oldTag) { 
        
                           buildMessageFragmentForValue( 
        
                               PolicyUtils.getCleanedTagName(newTag), 
        
                               PolicyUtils.getCleanedTagName(oldTag), 
        
                               policyTagListName, 
        
                               true, 
        
                               setFragments, 
        
                               removalFragments, 
        
                               changeFragments, 
        
                               policyTagListName === localizedTagListName, 
        
                           ); 
        
                       } 
        
                   }); 
        
               } 
        
               const hasModifiedBillable = reportActionOriginalMessage && 'oldBillable' in reportActionOriginalMessage && 'billable' in reportActionOriginalMessage; 
        
               if (hasModifiedBillable) { 
        
                   buildMessageFragmentForValue( 
        
                       reportActionOriginalMessage?.billable ?? '', 
        
                       reportActionOriginalMessage?.oldBillable ?? '', 
        
                       Localize.translateLocal('iou.request'), 
        
                       true, 
        
                       setFragments, 
        
                       removalFragments, 
        
                       changeFragments, 
        
                   ); 
        
               } 
        
               const message = 
        
                   getMessageLine(`\n${Localize.translateLocal('iou.changed')}`, changeFragments) + 
        
                   getMessageLine(`\n${Localize.translateLocal('iou.set')}`, setFragments) + 
        
                   getMessageLine(`\n${Localize.translateLocal('iou.removed')}`, removalFragments); 
        
               if (message === '') { 
        
                   return Localize.translateLocal('iou.changedTheRequest'); 
        
               } 
        
               return `${message.substring(1, message.length)}`; 
        
           }

paultsimura · 2024-03-06T19:00:58Z

@thienlnam I have implemented the localizable optimistic actions. So if you haven't updated the API on the BE, I'll share the object type I'm currently expecting optimistically, please share what you think about it:

type OriginalMessageTaskEdited = {
    actionName: typeof CONST.REPORT.ACTIONS.TYPE.TASKEDITED;
    originalMessage: {
        oldTitle?: string;
        title?: string;
        oldDescription?: string;
        description?: string;
        oldAssigneeAccountID?: number;
        assigneeAccountID?: number;
    };
};

This way, the originalMessage will be as close to the MODIFIEDEXPENSE as possible: it will hold only oldValue and value of the field that was modified.
Besides that, storing the oldValue will allow displaying messages in a format like: updated the description to "new" (previously "old") if we want to.

thienlnam · 2024-03-06T19:15:11Z

I should have clarified but let's move forward without localization in this PR - localization is not a current priority so while I've added it to the list - it may be a while until we decide to reprioritize those changes

This reverts commit a86a2f7.

paultsimura · 2024-03-06T19:39:39Z

Got you. Then we're good to test again @eVoloshchak.

eVoloshchak

Tested this by cherry-picking the PR into the latest main, works well, approving
@paultsimura, could you resolve the conflicts please?

# Conflicts: # src/pages/home/report/ReportActionItem.tsx

thienlnam · 2024-03-07T18:39:28Z

Getting some type errors cc @paultsimura

Error: src/libs/actions/Task.ts(483,93): error TS2345: Argument of type 'number | null' is not assignable to parameter of type 'number'.
  Type 'null' is not assignable to type 'number'.

paultsimura · 2024-03-07T18:43:23Z

Getting some type errors

Should be resolved now, let's see what the CI will say...

thienlnam · 2024-03-07T19:02:38Z

All set - thanks for the quick work on this!

OSBotify · 2024-03-07T19:08:29Z

✋ 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 · 2024-03-08T00:03:32Z

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

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

OSBotify · 2024-03-12T18:38:00Z

🚀 Deployed to production by https://github.com/luacmartins in version: 1.4.50-5 🚀

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

hungvu193 · 2024-03-18T15:35:00Z

src/libs/OptionsListUtils.ts

-    ) {
-        lastMessageTextFromReport = lastReportAction?.message?.[0].text ?? '';
+    } else if (ReportActionUtils.isTaskAction(lastReportAction)) {
+        lastMessageTextFromReport = TaskUtils.getTaskReportActionMessage(lastReportAction).text;


This line will introduce the regression #37976, causing the last message text to become multiple lines in the LHN. So I think in the future whenever we develop a feature that relate to text, we should also test the text overflow case.

shubham1206agra · 2024-08-07T01:56:41Z

src/libs/ReportUtils.ts

-                text: ' edited this task',
+                type: CONST.REPORT.MESSAGE.TYPE.COMMENT,
+                text: `assigned to ${getDisplayNameForParticipant(assigneeAccountID)}`,
+                html: `assigned to <mention-user accountID=${assigneeAccountID}></mention-user>`,


This line created a bug where LHN won't show the user. See more details on #45167

Build optimistic Edit Task actions

aefde12

paultsimura force-pushed the fix/36196-edit-task branch from b141130 to aefde12 Compare February 19, 2024 16:00

paultsimura mentioned this pull request Feb 20, 2024

[HOLD for payment 2024-03-18] [$500] Add edit system messages for tasks #36196

Closed

paultsimura added 2 commits February 20, 2024 23:09

Merge branch 'main' into fix/36196-edit-task

ab40861

DRY

c4dcda1

Merge branch 'main' into fix/36196-edit-task

2b92139

No longer hide the TASKEDITED actions

adc314e

Merge branch 'main' into fix/36196-edit-task

90186b2

Merge branch 'main' into fix/36196-edit-task

e76fa93

Reformat task-related actions

c35a510

paultsimura force-pushed the fix/36196-edit-task branch from f47262f to c35a510 Compare February 29, 2024 01:16

Merge branch 'main' into fix/36196-edit-task

f89025c

Localize taskEdited messages

a86a2f7

paultsimura marked this pull request as draft March 6, 2024 19:04

Revert "Localize taskEdited messages"

f3e618e

This reverts commit a86a2f7.

paultsimura marked this pull request as ready for review March 6, 2024 19:39

eVoloshchak approved these changes Mar 7, 2024

View reviewed changes

melvin-bot bot requested a review from thienlnam March 7, 2024 18:29

Merge branch 'main' into fix/36196-edit-task

c1a0fd0

# Conflicts: # src/pages/home/report/ReportActionItem.tsx

Fix TS error

e7031e4

thienlnam approved these changes Mar 7, 2024

View reviewed changes

thienlnam merged commit 6b7b972 into Expensify:main Mar 7, 2024
15 checks passed

github-actions bot mentioned this pull request Mar 7, 2024

Deploy Checklist: New Expensify 2024-03-07 #37938

Closed

43 tasks

paultsimura mentioned this pull request Mar 8, 2024

[HOLD #374470][$500] Task system message is not translated to Spanish #37943

Closed

6 tasks

luacmartins mentioned this pull request Mar 8, 2024

[HOLD 374470]Task - System message does not appear for user B when editing task until page refreshed #37994

Closed

6 tasks

marcaaron mentioned this pull request Mar 8, 2024

[HOLD - #374470] Thread header and LHN for task assignee system message is missing the assignee #37939

Closed

6 tasks

hungvu193 reviewed Mar 18, 2024

View reviewed changes

hungvu193 mentioned this pull request Mar 18, 2024

[HOLD for payment 2024-03-19]Task - Multi-line task descriptions are not truncated in the LHN #37976

Closed

6 tasks

shubham1206agra reviewed Aug 7, 2024

View reviewed changes

shubham1206agra mentioned this pull request Aug 7, 2024

[HOLD for payment 2024-08-05] [$250] Task – Assignee appears in LHN only after go back online if change it offline #45167

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: Build optimistic Edit Task actions #36768

feat: Build optimistic Edit Task actions #36768

paultsimura commented Feb 17, 2024 •

edited

Loading

paultsimura commented Feb 19, 2024

thienlnam commented Feb 20, 2024

paultsimura commented Feb 20, 2024

paultsimura commented Feb 20, 2024

thienlnam commented Feb 20, 2024

paultsimura commented Feb 20, 2024

thienlnam commented Feb 21, 2024

paultsimura commented Feb 21, 2024 •

edited

Loading

thienlnam commented Feb 21, 2024

paultsimura commented Feb 21, 2024

thienlnam commented Feb 21, 2024

paultsimura commented Feb 21, 2024

thienlnam commented Feb 21, 2024

thienlnam commented Feb 27, 2024

paultsimura commented Feb 28, 2024 •

edited

Loading

paultsimura commented Feb 28, 2024

paultsimura commented Feb 28, 2024 •

edited

Loading

thienlnam commented Feb 29, 2024

paultsimura commented Feb 29, 2024 •

edited

Loading

paultsimura commented Mar 4, 2024

paultsimura commented Mar 4, 2024 •

edited

Loading

paultsimura commented Mar 6, 2024

thienlnam commented Mar 6, 2024

paultsimura commented Mar 6, 2024

eVoloshchak left a comment •

edited

Loading

thienlnam commented Mar 7, 2024

paultsimura commented Mar 7, 2024

thienlnam commented Mar 7, 2024

OSBotify commented Mar 7, 2024

OSBotify commented Mar 8, 2024

OSBotify commented Mar 12, 2024

hungvu193 Mar 18, 2024

shubham1206agra Aug 7, 2024

feat: Build optimistic Edit Task actions #36768

feat: Build optimistic Edit Task actions #36768

Conversation

paultsimura commented Feb 17, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

paultsimura commented Feb 19, 2024

thienlnam commented Feb 20, 2024

paultsimura commented Feb 20, 2024

paultsimura commented Feb 20, 2024

thienlnam commented Feb 20, 2024

paultsimura commented Feb 20, 2024

thienlnam commented Feb 21, 2024

paultsimura commented Feb 21, 2024 • edited Loading

thienlnam commented Feb 21, 2024

paultsimura commented Feb 21, 2024

thienlnam commented Feb 21, 2024

paultsimura commented Feb 21, 2024

thienlnam commented Feb 21, 2024

thienlnam commented Feb 27, 2024

paultsimura commented Feb 28, 2024 • edited Loading

paultsimura commented Feb 28, 2024

paultsimura commented Feb 28, 2024 • edited Loading

thienlnam commented Feb 29, 2024

paultsimura commented Feb 29, 2024 • edited Loading

paultsimura commented Mar 4, 2024

paultsimura commented Mar 4, 2024 • edited Loading

paultsimura commented Mar 6, 2024

thienlnam commented Mar 6, 2024

paultsimura commented Mar 6, 2024

eVoloshchak left a comment • edited Loading

Choose a reason for hiding this comment

thienlnam commented Mar 7, 2024

paultsimura commented Mar 7, 2024

thienlnam commented Mar 7, 2024

OSBotify commented Mar 7, 2024

OSBotify commented Mar 8, 2024

OSBotify commented Mar 12, 2024

hungvu193 Mar 18, 2024

Choose a reason for hiding this comment

shubham1206agra Aug 7, 2024

Choose a reason for hiding this comment

paultsimura commented Feb 17, 2024 •

edited

Loading

paultsimura commented Feb 21, 2024 •

edited

Loading

paultsimura commented Feb 28, 2024 •

edited

Loading

paultsimura commented Feb 28, 2024 •

edited

Loading

paultsimura commented Feb 29, 2024 •

edited

Loading

paultsimura commented Mar 4, 2024 •

edited

Loading

eVoloshchak left a comment •

edited

Loading