Fix: IOU description can't be seen on the LHN reports #34840

tobyjsullivan · 2024-01-19T21:19:52Z

Details

Update the translation iou.payerOwesAmount to include the IOU description when it is available.

Fixed Issues

$ #31859
PROPOSAL: #31859 (comment)

Tests

Steps to Reproduce

Navigate to https://dev.new.expensify.com:8082/
Click avatar at top of LHN to open "Settings"
Click "Preferences"
Set "Priority mode" to "Most recent"
Click the FAB to open menu.
Click "Request Money".
Select "Manual" entry.
Enter amount of 5000 and click "Next".
Enter email for another member and click the suggestion.
Enter a description (e.g., "Ramen dinner")
Click "Request $5000.00" to create the IOU
Find the IOU report in LHN for one of the members.
Verify the description is included in the report preview in the LHN.

Tests

Size window to full-size. Observe the IOU description is included in the LHN on desktop view.
- Note: if the email address is too long, this can be verified by inspecting the element in Chrome dev tools.
Resize screen to mobile size, click back arrow to view LHN. Observe description appears on IOU report.
Verify that no errors appear in the JS console.
Create a new split IOU with no description. Confirm the LHN record displays the amount without a description.
Split the IOU between multiple members.
Edit the amount of an IOU.

Offline tests

Throttle network (in Chrome dev tools).
Ensure LHN still renders correctly.

QA Steps

Steps to Reproduce

Navigate to https://staging.new.expensify.com/
Sign into an account with a workspace
Click avatar at top of LHN to open "Settings"
Click "Preferences"
Set "Priority mode" to "Most recent"
Click the FAB to open menu.
Click "Request Money".
Select "Manual" entry.
Enter amount of 5000 and click "Next".
Enter email for another member and click the suggestion.
Enter a description (e.g., "Ramen dinner")
Click "Request $5000.00" to create the IOU
Find the IOU report in LHN for one of the members.
Verify the report subtitle includes the description.
- You may need to resize the browser window to mobile size to see the full description (see screenshots below for examples)

Tests

Size window to full-size. Observe the IOU description is included in the LHN on desktop view.
- Note: if the email address is too long, this can be verified by inspecting the element in Chrome dev tools.
Resize screen to mobile size, click back arrow to view LHN. Observe description appears on IOU report.
Verify that no errors appear in the JS console.
Create a new IOU with no description. Confirm the LHN record displays the amount without a description.
Split the request between multiple members.
Edit the amount of the money request and verify the description is updated.

PR Author Checklist

Screenshots/Videos

Android: Native

Note: change is not actually visible on Android. However, tests confirm no functionality is broken.

Expensify.31859.-.Test.006.-.Android.mov

Android: mWeb Chrome

Note: change is not actually visible on Android. However, tests confirm no functionality is broken.

Expensify.31859.-.Test.007.-.mWeb.Android.mov

iOS: Native

Note: change is not actually visible on iOS. However, tests confirm no functionality is broken.

Expensify.31859.-.Test.003.-.iOS.mov

iOS: mWeb Safari

Note: change is not actually visible on iOS. However, tests confirm no functionality is broken.

Expensify.31859.-.Test.004.-.mWeb.iOS.mov

MacOS: Chrome / Safari

Expensify.31859.-.Test.002.mov

MacOS: Desktop

Expensify.31859.-.Test.005.-.Desktop.macOS.mov

github-actions · 2024-01-19T21:20:06Z

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

tobyjsullivan · 2024-01-19T21:58:52Z

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

melvin-bot · 2024-01-22T18:57:54Z

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

dangrous · 2024-01-24T16:42:54Z

hey @parasharrajat! Do you have time to take a look at this today? Thanks!

parasharrajat · 2024-01-24T16:54:25Z

I will get on it.

parasharrajat · 2024-01-24T18:06:23Z

src/libs/ReportUtils.ts

+        const reportTransactions = !isEmptyObject(report) ? TransactionUtils.getAllReportTransactions(report.reportID) : [];
+        const comment = reportTransactions.length === 1 ? TransactionUtils.getDescription(reportTransactions[0]) : undefined;
+        return Localize.translateLocal('iou.payerOwesAmount', {payer: payerOrApproverName, amount: formattedAmount, comment});


Why do we have to change this?

The translation is being updated to include the description from money requests.

I think you didn't understand the question. I am asking why we have to change this part of the code. Do we need to pass comment here to solve the issue? What does it change in UI?

-- Please reply to all three comments.

Okay, thanks for the clarification. Re-reading the discussion on the original issue, I think I misunderstood this comment.

Correct, let's change the existing one and adjust it where used.

I originally interpreted this to mean we should include the description everywhere the translation is used. However, now I see that's not what you meant. Instead, you meant we can use the same translation everywhere and other places would not need to change.

I can revert the changes to these blocks. Please confirm if that's the preferred course of action.

Yeah, correct. I would also suggest to check if we are not missing this comment anywhere else. For now, let's remove these updates where comments should not be shown. For example this one.

Done. I've reverted changes to all the text unrelated to the original issue.

parasharrajat · 2024-01-24T18:13:10Z

src/libs/actions/IOU.js

+        const comment = !isEmptyObject(transaction) ? TransactionUtils.getDescription(transaction) : undefined;
+        messageText = Localize.translateLocal('iou.payerOwesAmount', {payer, amount: formattedAmount, comment});
+    }
+


Same for these. Why do we have to change these chunks?

The previous code used a ternary operation to select which translation is used, then the same parameters were passed in either case.

Now, the iou.payerOwesAmount translation is being updated to accept a description from money requests. As a result, the translations no longer accept the same parameters and the previous ternary branch is no longer an option.

Okay, thanks for the clarification. Re-reading the discussion on the original issue, I think I misunderstood this comment.

Correct, let's change the existing one and adjust it where used.

I originally interpreted this to mean we should include the description everywhere the translation is used. However, now I see that's not what you meant. Instead, you meant we can use the same translation everywhere and other places would not need to change.

I can revert the changes to these blocks. Please confirm if that's the preferred course of action.

parasharrajat · 2024-01-24T18:13:18Z

src/libs/actions/IOU.js

+        const payer = ReportUtils.getPersonalDetailsForAccountID(updatedMoneyRequestReport.managerID).login || '';
+        const formattedAmount = CurrencyUtils.convertToDisplayString(updatedMoneyRequestReport.total, updatedMoneyRequestReport.currency);
+        let messageText;
+        if (hasNonReimbursableTransactions) {
+            messageText = Localize.translateLocal('iou.payerSpentAmount', {payer, amount: formattedAmount});
+        } else {
+            const comment = TransactionUtils.getDescription(updatedTransaction);
+            messageText = Localize.translateLocal('iou.payerOwesAmount', {payer, amount: formattedAmount, comment});
+        }
+


Same for these. Why do we have to change these chunks?

The previous code used a ternary operation to select which translation is used, then the same parameters were passed in either case.

Now, the iou.payerOwesAmount translation is being updated to accept a description from money requests. As a result, the translations no longer accept the same parameters and the previous ternary branch is no longer an option.

Okay, thanks for the clarification. Re-reading the discussion on the original issue, I think I misunderstood this comment.

Correct, let's change the existing one and adjust it where used.

I originally interpreted this to mean we should include the description everywhere the translation is used. However, now I see that's not what you meant. Instead, you meant we can use the same translation everywhere and other places would not need to change.

I can revert the changes to these blocks. Please confirm if that's the preferred course of action.

tobyjsullivan · 2024-01-26T18:37:46Z

Updated

parasharrajat · 2024-01-30T07:45:06Z

OK, so I noticed one issue. Your PR works great for split requests.

There are a few types of chat in the app.

DM
Group Chat.
1-1 money report.
1-Many split money report. (this also creates 1-1 money report between all the users and the request is sent as a message to each DM between these users).

You fixed the issue for DM between users when we split among users but the issue is still present for 1-1 money report.

Here in the below image, you can see that split chat report has description but it is not present not for request report between two users.

In the image,
DM = 1-1 money report.
Group Split = 1-Many split money report.

tobyjsullivan · 2024-01-30T17:56:07Z

@parasharrajat Okay, good call. I've pushed a commit which adds the comment for that translation.

I can see in the code that there are other cases that probably need a translation (namely, ${name} spent ${amount}). However, I cannot figure out how to get these cases to show in the UI. Do you know what case would put that in the LHN or should I leave that alone for now?

tobyjsullivan · 2024-02-01T21:29:09Z

Updated

parasharrajat · 2024-02-05T12:13:26Z

@tobyjsullivan Could you please merge main?

parasharrajat · 2024-02-27T19:51:11Z

I will check it shortly. Thanks for your patience.

parasharrajat · 2024-03-04T14:00:13Z

src/libs/ReportUtils.ts

@@ -2296,6 +2296,7 @@ function getReportPreviewMessage(
    isPreviewMessageForParentChatReport = false,
    policy: OnyxEntry<Policy> = null,
    isForListPreview = false,
+    originalReportAction: OnyxEntry<ReportAction> | EmptyObject = reportAction,


I am trying to understand the difference between this and reportAction. Can you please describe this?

You are correct that they are very similar but there is one case where the values differ.

In general, reportAction should be the message for which the preview is being generated. However, a different action is passed for reportAction when generating the LHN message for a report preview (a message grouping multiple money requests - see screenshot below for an example).

App/src/libs/OptionsListUtils.ts

Lines 558 to 573 in 49cb3b1

} else if (ReportActionUtils.isReportPreviewAction(lastReportAction)) {

const iouReport = ReportUtils.getReport(ReportActionUtils.getIOUReportIDFromReportActionPreview(lastReportAction));

const lastIOUMoneyReportAction = allSortedReportActions[iouReport?.reportID ?? '']?.find(

(reportAction, key) =>

ReportActionUtils.shouldReportActionBeVisible(reportAction, key) &&

reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE &&

ReportActionUtils.isMoneyRequestAction(reportAction),

);

lastMessageTextFromReport = ReportUtils.getReportPreviewMessage(

!isEmptyObject(iouReport) ? iouReport : null,

lastIOUMoneyReportAction,

true,

ReportUtils.isChatReport(report),

null,

true,

);

I believe this is a bug and should be fixed separately.

To generate the correct preview text for a report preview action, we need a way to access the original preview action so that we can determine the number of child reports in the preview. To solve this, I pass the original as originalReportAction while leaving reportAction unchanged. (Fixing the value of reportAction would blow out the scope of this PR, particularly around QA/validation, so I've decided not to do that.)

Visual Example

Here is an example of a "report preview" message. In this case, reportAction should be the last message (the only message, in this particular case). However, in practice, reportAction is one of the child money request reports. To correct for this, the actual preview message is passed as originalReportAction.

let's rename the reportAction param to previewReportAction to make it more clear. Also add a comment explaining the differences between both on the definition.

Okay, done with one tweak. I renamed reportAction to iouReportAction as I think this will be less confusing to readers. Hopefully the comments clarify why this name makes sense.

Thanks. But I don't think that the previous reportAction was only an iOU report action. It can be linked to a normal DM as well. Why do you think iouReportAction is better name?

The previous comment suggested reportAction could be either a report preview or an IOU report action so perhaps that comment is incorrect.

App/src/libs/ReportUtils.ts

Line 2334 in 98129e6

* @param [reportAction] This can be either a report preview action or the IOU action

I did not want to rename reportAction to previewReportAction because that name implies the action is a report preview. This would be confusing because the value is never a report preview action (as far as I can tell).

I chose iouReportAction because it seemed the report action could only be an IOU report action. However, if that's not true and it can also be a normal DM, then I no longer believe iouReportAction is the better name.

Do you still consider previewReportAction to be the correct choice?

This sounds good. I think the action can only be an iOU report action or an iou Preview Action.

tobyjsullivan · 2024-03-06T21:34:47Z

Updated

parasharrajat · 2024-03-11T09:29:36Z

r### Screenshots

🔲 iOS / native

Screen.Recording.2024-03-12.at.3.10.26.PM.mov

🔲 iOS / Safari

Screen.Recording.2024-03-12.at.3.14.15.PM.mov

🔲 MacOS / Desktop

Screen.Recording.2024-03-12.at.3.15.12.PM.mov

🔲 MacOS / Chrome

Screen.Recording.2024-03-11.at.5.19.22.PM.mov

🔲 Android / Chrome

Screen.Recording.2024-03-12.at.3.09.07.PM.mov

🔲 Android / native

Screen.Recording.2024-03-12.at.3.06.16.PM.mov

parasharrajat · 2024-03-11T18:13:42Z

Just waiting on the iOS Build error PR so that I can finish the checklist.

parasharrajat · 2024-03-11T18:43:03Z

@tobyjsullivan Please merge main so that I can test iOS.

tobyjsullivan · 2024-03-11T22:26:43Z

Updated

parasharrajat

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: mWeb Chrome
- iOS: Native
- iOS: mWeb 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(theme.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 the PR modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label so the design team can review the changes.
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.

🎀 👀 🎀 C+ reviewed

parasharrajat · 2024-03-12T10:23:08Z

There is a bug with the Send Money flow where clicking the description shows not found page. This is also present on staging not related to this PR.

Reported: https://expensify.slack.com/archives/C049HHMV9SM/p1710239078914799

dangrous

Cool, this works for me!

dangrous · 2024-03-12T15:24:17Z

Blargh can you try merging main and see if that fixes those performance tests? thanks!

dangrous · 2024-03-18T15:58:05Z

Bump the above ^ @tobyjsullivan - would like to get this merged this week. Thanks!

parasharrajat · 2024-03-18T21:33:03Z

@dangrous Ready for review.

tobyjsullivan · 2024-03-18T21:39:21Z

Thanks for the nudge. I'd missed that request. Latest main is merged in now.

dangrous

LGTM!

melvin-bot · 2024-03-19T17:48:22Z

@dangrous looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

OSBotify · 2024-03-19T23:50:22Z

🚀 Deployed to staging by https://github.com/dangrous in version: 1.4.55-0 🚀

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

OSBotify · 2024-03-20T00:50:57Z

🚀 Deployed to staging by https://github.com/dangrous in version: 1.4.55-0 🚀

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

OSBotify · 2024-03-22T16:09:43Z

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.4.55-3 🚀

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

tobyjsullivan added 5 commits January 19, 2024 09:27

Include comment in report name for amounts owing

bd5f177

Reuse translateLocal call

ee2c15d

Remove redundant type declaration

eeca194

Avoid variable reassignments

db0d8d1

Remove unrelated code change

c2731c0

tobyjsullivan added 5 commits January 19, 2024 14:51

Update editRegularMoneyTransaction

036ac5c

Include request description when request deleted

40073f0

Include IOU description in report name

f7032dd

Run prettier and lint

2e2ac1f

Merge branch 'main' into fix/31859

62035fc

tobyjsullivan marked this pull request as ready for review January 22, 2024 18:57

tobyjsullivan requested a review from a team as a code owner January 22, 2024 18:57

melvin-bot bot requested review from parasharrajat and removed request for a team January 22, 2024 18:57

parasharrajat suggested changes Jan 24, 2024

View reviewed changes

Undo changes to text outside LHN preview

719d63d

tobyjsullivan requested a review from parasharrajat January 29, 2024 21:03

Display report description for 1-to-1 money request

e48ebb1

tobyjsullivan added 2 commits February 6, 2024 08:04

Merge branch 'main' into fix/31859

a3af0b1

Fix prettier formatting

1ad742d

parasharrajat reviewed Mar 4, 2024

View reviewed changes

tobyjsullivan added 2 commits March 6, 2024 13:14

Merge branch 'main' into fix/31859

40b0c6f

Add and update comments for report action params

89418e8

Merge branch 'main' into fix/31859

7bf59f8

parasharrajat approved these changes Mar 12, 2024

View reviewed changes

melvin-bot bot requested a review from dangrous March 12, 2024 09:49

dangrous previously approved these changes Mar 12, 2024

View reviewed changes

Merge branch 'main' into fix/31859

defc91c

tobyjsullivan dismissed dangrous’s stale review via defc91c March 18, 2024 21:16

dangrous approved these changes Mar 19, 2024

View reviewed changes

dangrous merged commit 73ecb3f into Expensify:main Mar 19, 2024
16 checks passed

melvin-bot bot added the Emergency label Mar 19, 2024

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

Deploy Checklist: New Expensify 2024-03-19 #38651

Closed

66 tasks

melvin-bot bot mentioned this pull request Mar 22, 2024

[HOLD for payment 2024-03-29] [LOW] [Splits] [$500] IOU - IOU description can't be seen on the LHN reports #31859

Closed

6 tasks

parasharrajat mentioned this pull request Apr 3, 2024

[HOLD for payment 2024-04-15] [$500] IOU - Multiline IOU description from 1:1 DM in LHN is not truncated #39437

Closed

6 tasks

	} else if (ReportActionUtils.isReportPreviewAction(lastReportAction)) {
	const iouReport = ReportUtils.getReport(ReportActionUtils.getIOUReportIDFromReportActionPreview(lastReportAction));
	const lastIOUMoneyReportAction = allSortedReportActions[iouReport?.reportID ?? '']?.find(
	(reportAction, key) =>
	ReportActionUtils.shouldReportActionBeVisible(reportAction, key) &&
	reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE &&
	ReportActionUtils.isMoneyRequestAction(reportAction),
	);
	lastMessageTextFromReport = ReportUtils.getReportPreviewMessage(
	!isEmptyObject(iouReport) ? iouReport : null,
	lastIOUMoneyReportAction,
	true,
	ReportUtils.isChatReport(report),
	null,
	true,
	);

Fix: IOU description can't be seen on the LHN reports #34840

Fix: IOU description can't be seen on the LHN reports #34840

Conversation

tobyjsullivan commented Jan 19, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

github-actions bot commented Jan 19, 2024 • edited Loading

tobyjsullivan commented Jan 19, 2024

melvin-bot bot commented Jan 22, 2024

dangrous commented Jan 24, 2024

parasharrajat commented Jan 24, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

parasharrajat Jan 25, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tobyjsullivan commented Jan 26, 2024

parasharrajat commented Jan 30, 2024

tobyjsullivan commented Jan 30, 2024

tobyjsullivan commented Feb 1, 2024

parasharrajat commented Feb 5, 2024

parasharrajat commented Feb 27, 2024

Choose a reason for hiding this comment

tobyjsullivan Mar 4, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

parasharrajat Mar 6, 2024 • edited Loading

Choose a reason for hiding this comment

tobyjsullivan Mar 6, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tobyjsullivan commented Mar 6, 2024

parasharrajat commented Mar 11, 2024 • edited Loading

🔲 iOS / native

🔲 iOS / Safari

🔲 MacOS / Desktop

🔲 MacOS / Chrome

🔲 Android / Chrome

🔲 Android / native

parasharrajat commented Mar 11, 2024 • edited Loading

parasharrajat commented Mar 11, 2024

tobyjsullivan commented Mar 11, 2024

parasharrajat left a comment

Choose a reason for hiding this comment

Reviewer Checklist

parasharrajat commented Mar 12, 2024 • edited Loading

dangrous left a comment

Choose a reason for hiding this comment

dangrous commented Mar 12, 2024

dangrous commented Mar 18, 2024

parasharrajat commented Mar 18, 2024

tobyjsullivan commented Mar 18, 2024

dangrous left a comment

Choose a reason for hiding this comment

melvin-bot bot commented Mar 19, 2024

OSBotify commented Mar 19, 2024

OSBotify commented Mar 20, 2024

OSBotify commented Mar 22, 2024

tobyjsullivan commented Jan 19, 2024 •

edited

Loading

github-actions bot commented Jan 19, 2024 •

edited

Loading

parasharrajat Jan 25, 2024 •

edited

Loading

tobyjsullivan Mar 4, 2024 •

edited

Loading

parasharrajat Mar 6, 2024 •

edited

Loading

tobyjsullivan Mar 6, 2024 •

edited

Loading

parasharrajat commented Mar 11, 2024 •

edited

Loading

parasharrajat commented Mar 11, 2024 •

edited

Loading

parasharrajat commented Mar 12, 2024 •

edited

Loading