Bank account and Authorized payer buttons displayed instead of Connect bank account #40182

ikevin127 · 2024-04-12T18:36:50Z

Details

Everytime we toggle "Make or track payments" we set the achAccount: {reimburser: reimburserEmail} and the UI ends up looking like we have a bank account added because of this hasVBA check, when we don't actually have a bank account added yet.

To fix this we changed the hasVBA to check when we actually have a BA by checking for bankAccountID, additionally added the isLoadingWorkspaceReimbursement for the SetWorkspaceReimbursement call in order to show a loading spinner when we toggle "Make or track payments", instead of having the UI jump from the "Connect bank account" button to "Bank account" and "Authorized payer" buttons.

Small refactor: added shouldShowBankAccount variable because there were 3 occurances of this check.

Fixed Issues

$ #39947
PROPOSAL: #39947 (comment)

Tests

Create a new workspace.
Go to Workspace > More features and enable Workflows
Go to Workspace > Workflows and under Make or track payments tap on Connect bank account.
Go back.
Disable Make or track payments then enable it again.
Verify that only the Connect bank account button is visible.

Verify that no errors appear in the JS console

Offline tests

TLDR: same as Tests.

Create a new workspace.
Go to Workspace > More features and enable Workflows
Go to Workspace > Workflows and under Make or track payments tap on Connect bank account.
Go back.
Disable Make or track payments then enable it again.
Verify that only the Connect bank account button is visible.

QA Steps

TLDR: same as Tests.

Create a new workspace.
Go to Workspace > More features and enable Workflows
Go to Workspace > Workflows and under Make or track payments tap on Connect bank account.
Go back.
Disable Make or track payments then enable it again.
Verify that only the Connect bank account button is visible.

Additional tests from PR:

Replaces usage of reimburserEmail with achAccount.reimburser #39017:

Preconditions: Having a policy with VBA and some Admins.

Happy path:

Open Settings > Workspaces > > Workflows.
See that you have an Authorized payer.
Click on the Authorized payer and change it to a different one.
Now, change it to one that has a display name set and check that the display name is shown under Authorized payer.

Error path:

Open Settings > Workspaces > > Workflows.
See that you have an Authorized payer.
Go offline and change the Authorized payer.
In a different tab/browser demote the Authorized payer from step 3 to Member.
Go back to the offline tab and get back online, the Authorized payer should get reverted to the previous one and there should be a red dot next to it indicating that it could not update.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android.mov

Android: mWeb Chrome

android-mweb.mov

iOS: Native

ios.mov

iOS: mWeb Safari

ios-mweb.mov

MacOS: Chrome / Safari

without-ba.mov

MacOS: Desktop

desktop.mov

…t bank account

melvin-bot · 2024-04-12T18:36:55Z

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

shawnborton · 2024-04-14T18:43:34Z

I think this looks pretty good, cc @Expensify/design (you too Tom) for extra eyes on the loading spinner pattern here.

dubielzyk-expensify · 2024-04-15T00:30:24Z

Looks good to me as well

trjExpensify · 2024-04-15T09:56:25Z

I think this looks pretty good, cc @Expensify/design (you too Tom) for extra eyes on the loading spinner pattern here.

Yeah, I think the loading spinner is fine. It would be great if we could minimise that time to load, but this works for sure.

ikevin127 · 2024-04-15T13:45:40Z

♻ Fixed conflict by removing unused type export ACHAccount, ready for review!

It would be great if we could minimise that time to load, but this works for sure.

@trjExpensify We can involve BE for this in a separate task regarding the SetWorkspaceReimbursement call, and I'd also make sure this bug that I found mentioned in #39947 (comment) is looked into by BE if they're going to try and minimise time to load for the SetWorkspaceReimbursement call.

ishpaul777 · 2024-04-16T11:13:16Z

Sorry it took me a while to get to this, reviewing now

ishpaul777 · 2024-04-16T11:14:14Z

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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- 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 UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design 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.

Screenshots/Videos

Android: Native

Record_2024-05-17-16-20-18.mp4

Android: mWeb Chrome

Record_2024-05-17-16-48-49.mp4

iOS: Native

trim.0E6E945D-D25B-49BD-85BB-2E8223C1DD75.MOV

iOS: mWeb Safari

trim.46D089D1-2583-4D37-8C3A-74128F63ADAD.MOV

MacOS: Chrome / Safari

BA added- (with and without internet)

Screen.Recording.2024-05-17.at.1.17.46.AM-1.mov

No BA added - (with and without internet)

Screen.Recording.2024-05-17.at.12.25.37.AM.mov

MacOS: Desktop

Screen.Recording.2024-05-17.at.5.00.55.PM.mov

ishpaul777 · 2024-04-16T12:01:52Z

bug: Infinite loading when toggling the button offline.

and loading time in general is too long, i have never seen this type of loading pattern (loading for everytime user toggle on) anywhere in App we generally set all necesary optimistc data to avoid this

Screen.Recording.2024-04-16.at.5.26.43.PM.mov

ikevin127 · 2024-04-16T12:15:17Z

@ishpaul777 Good catch, I'll address the offline case of the spinner.

Regarding the seemingly long SetWorkspaceReimbursement call time to fulfil, this was addressed above in #40182 (comment), and as far as this fix is concerned we're fine with that.

ikevin127 · 2024-04-16T12:54:23Z

@ishpaul777 Fixed the infinite loading while offline bug. Let me know if you find any other issues with this PR!

trjExpensify · 2024-04-16T12:59:17Z

♻ Fixed conflict by removing unused type export ACHAccount, ready for review!

It would be great if we could minimise that time to load, but this works for sure.

@trjExpensify We can involve BE for this in a separate task regarding the SetWorkspaceReimbursement call, and I'd also make sure this bug that I found mentioned in #39947 (comment) is looked into by BE if they're going to try and minimise time to load for the SetWorkspaceReimbursement call.

Ah, interesting. @lakchote might have some insight on that!

ishpaul777 · 2024-04-17T21:36:25Z

@ikevin127 Can you please merge main quickly

ikevin127 · 2024-04-17T21:40:47Z

@ishpaul777 ✅

ishpaul777 · 2024-04-17T21:48:59Z

instead of having the UI jump from the "Connect bank account" button to "Bank account" and "Authorized payer" buttons.

Thinking more about the loader it just feels off pattern, can you please share a recording for the "jump" that you mentioned in PR decription and do we get this everytime. I believe the loading is dependent on user network condition more than how much backend is optimized right? so in case user network is slow it just have long loader, which is exactly we want to avoid with have optimisticData set for every request

ikevin127 · 2024-04-17T23:27:58Z

Indeed, ultimately the Workflow's no-BA / BA flow should be re-considered from a BE point of view and fixed properly on the FE side as all the proposals from this issue (including mine) are undesired workarounds (IMO) that don't really address the flow completely from the following points of view:
~~- seamless UI/UX~~
~~- happy path / unhappy path~~
~~- offline / online transiton (optimistically)~~
~~- BE response time regarding BA details (too slow currently)~~
- correct SetWorkspaceReimbursementcall (currently it's not doing what it's supposed to do [set reimbursment], but doing extra things besides that), see #39947 (comment) bullet number 2 for more details)

~~cc @lakchote @ishpaul777~~

ishpaul777 · 2024-04-20T19:38:10Z

FYI i'll be OOO until tuesday and will be partially available after that until 29 April.

Status for the PR: I feel the usage of loader here is not our pattern so i am not inclined to approve it, If anyone disagrees i'd love to hear a different POV, as of this comment from @ikevin127 i do agree there's a lot going on with command.

correct SetWorkspaceReimbursementcall (currently it's not doing what it's supposed to do [set reimbursment], but doing extra things besides that), see #39947 (comment) bullet number 2 for more details)

we have 2 ways to move this forward (that i could think of)

Move with loading indicator even if its not our pattern (my pov why i believe this: Bank account and Authorized payer buttons displayed instead of Connect bank account #40182 (comment))

I believe the loading is dependent on user network condition more than how much backend is optimized right? so in case user network is slow it just have long loader, which is exactly we want to avoid with have optimisticData set for every request

Remove the loading indicator, and let the "jump" stay as it is (i am not what exactly is the "jump" @ikevin127 refered to, it would be good to have a reference video : ) or steps to reproduce it. )

and the other one Kevin suggested #40182 (comment)

trjExpensify · 2024-05-08T18:20:40Z

What's going on here? We back to finish it off?

ikevin127 · 2024-05-08T18:28:21Z

@trjExpensify ~~If we want something solid here, it requires BE changes. Otherwise, I think FE only changes will only break the current functionality instead of actually improving the flow.~~

For more details see #40182 (comment). Additionally, I don't think any of the two options mentioned by #40182 (comment) are viable because we have BE related issues when it comes to the flow (mentioned in #40182 (comment)).

lakchote · 2024-05-09T09:22:48Z

Status for the PR: I feel the usage of loader here is not our pattern so i am not inclined to approve it, If anyone disagrees i'd love to hear a different POV, as of this comment from @ikevin127 i do agree there's a lot going on with command.

The loader pattern was initially approved by @Expensify/design team here.

@Expensify/design could you please check @ishpaul777's comment here regarding the infinite loader scenario?

trjExpensify · 2024-05-09T09:54:41Z

Why do we have to have an infinite loader when offline? Can't we do something like this?

shawnborton · 2024-05-09T11:49:11Z

Yeah, I like Tom's suggestion.

lakchote · 2024-05-17T10:08:36Z

@lakchote Can you help trigger a build for this PR so we can test this on real android devices ? This way we can hopefully move on with the review process!

Good idea, I've triggered a build and will let you know once it's ready.

github-actions · 2024-05-17T10:39:23Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/40182/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/40182/index.html

Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/40182/NewExpensify.dmg	https://40182.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

ishpaul777 · 2024-05-17T11:49:24Z

Thank you @lakchote for build.

i was not able to reproduce with ADHOC and dev on real device. I am assuming there might be some issue with API at that time.

ishpaul777 · 2024-05-17T11:50:21Z

@Expensify/design This is ready for you guys to review 🙇

shawnborton · 2024-05-17T12:10:23Z

Nice - are there updated screenshots for us to review?

ishpaul777 · 2024-05-17T12:12:32Z

Yes, reviewer checklist has the up to date videos for all platforms #40182 (comment)

shawnborton · 2024-05-17T13:05:32Z

In this screen, why does one row appear to be more faded out than the other?

Also, the two rows feel like they are too far apart. Is that something we can adjust here too?

ishpaul777 · 2024-05-17T14:54:49Z

src/pages/workspace/workflows/WorkspaceWorkflowsPage.tsx

-                                    : translate('workflowsPage.connectBankAccount')
-                            }
-                            description={bankDisplayName}
-                            disabled={isOffline || !isPolicyAdmin}


In this screen, why does one row appear to be more faded out than the other?

it seems to done quite intentionally even before this PR. that is for the case when there's no optimistic pending action but user is offline.

we can add a check !policy?.pendingFields?.reimbursementChoice && isOffline to solve this

Okay, I think we should not have it double-faded so let's definitely solve that

Note

The first disabled grayed-out fade comes from the "Make or track payments" toggle when toggled while offline.

The second one comes from Connect bank account / Bank account option which was and is disabled while offline.

Authorized payer option is enabled while offline -> meaning the Authorized payer can be changed optimistically. This is why this one doesn't get double disabled grayed-out fade when "Make or track payments" is toggled while offline.

ishpaul777:

we can add a check !policy?.pendingFields?.reimbursementChoice && isOffline to solve this

I don't think this logic is good since it would break the logic mentioned at (2.) where Connect bank account / Bank account option was and is supposed to be disabled while offline.

shawnborton:

Okay, I think we should not have it double-faded so let's definitely solve that

To do this, instead I would use Connect bank account / Bank account option shouldGreyOutWhenDisabled to not have the 2nd gray-out fade applied to the option when already applied from "Make or track payments" toggle.

Similarly, we have to do the same for the OfflineWithFeedback wrapper of Authorized payer option (3.) we add:

shouldDisableOpacity={isOffline && policy?.pendingFields?.reimbursementChoice && policy?.pendingFields?.reimburser}

in order to not double gray-out the Authorized payer if already applied from "Make or track payments" toggle, when Authorized payer is changed while offline. This is how it would look in all scenarios:

Without Bank account added:

Offline (can't add / change Connect bank account option)

Offline (with "Make or track payments" Toggled (optimistically))

With Bank account added:

Offline (can't add / change Bank account option)

Offline (with "Make or track payments" Toggled (optimistically))

Offline (with "Make or track payments" Toggled + Authorized payer changed (optimistically))

Offline (with "Make or track payments" Toggled + Authorized payer changed (optimistically) and hover on Authorized payer)

shouldDisableOpacity={isOffline && policy?.pendingFields?.reimbursementChoice && policy?.pendingFields?.reimburser}

^ - Writing it like this is specifically important for the below case, since we don't want to NOT gray out Authorized payer when changed offline (optimistically) in case "Make or track payments" was NOT toggled, by only writing it like:
❌ shouldDisableOpacity={policy?.pendingFields?.reimburser}
since that would NOT gray out the optimistically set Authorized payer, instead we want to gray it out, maintaining the pattern like so:

Offline (with "Make or track payments" Not Toggled + Authorized payer changed (optimistically))

Please let me know if we're in agreement with the changes mentioned above from a design / code POV.
Once agreed I'll push the changes!

cc @ishpaul777 @shawnborton

Thanks for detailed investigation @ikevin127, code wise looks good to me 👍

ishpaul777 · 2024-05-17T14:59:31Z

Also, the two rows feel like they are too far apart. Is that something we can adjust here too?

Yeah! we can def. do minor style adjustment. Currently both Menuitems has padding top 12px and margin-top 16px. What should be the ideal

shawnborton · 2024-05-17T15:36:52Z

Can we try the second menu item with no top margin? This way it's 12px + 12px away from the item above it.

ikevin127 · 2024-05-17T22:46:09Z

Can we try the second menu item with no top margin? This way it's 12px + 12px away from the item above it.

Did this for second menu item, this are the results:

Before	After

Please let me know if we're in agreement with the changes mentioned above. Once agreed I'll push the changes!

cc @shawnborton

shawnborton · 2024-05-20T14:31:02Z

Did this for second menu item, this are the results:

Looks great!

ikevin127 · 2024-05-20T18:57:44Z

@ishpaul777 Just pushed changes from here and here. PR is ready for review!

ishpaul777

LGTM!

ikevin127 · 2024-05-28T21:09:56Z

@lakchote Are we merging this soon ? I synced w/ main because it had conflicts.

lakchote · 2024-05-29T07:20:47Z

@lakchote Are we merging this soon ? I synced w/ main because it had conflicts.

There was a merge freeze. Now that it's been removed, I'm going to merge this.

OSBotify · 2024-05-29T07:29:19Z

✋ 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-05-29T09:41:54Z

🚀 Deployed to staging by https://github.com/lakchote in version: 1.4.77-0 🚀

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

OSBotify · 2024-05-30T21:24:43Z

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.77-11 🚀

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

OSBotify · 2024-05-30T22:36:41Z

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.77-11 🚀

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

Bank account and Authorized payer buttons displayed instead of Connec…

f9a3198

…t bank account

ikevin127 requested a review from a team as a code owner April 12, 2024 18:36

melvin-bot bot requested review from ishpaul777 and removed request for a team April 12, 2024 18:36

ikevin127 mentioned this pull request Apr 12, 2024

[HOLD for payment 2024-06-06] [$500] [Workflows] Bank account and Authorized payer buttons displayed instead of Connect bank account #39947

Closed

6 tasks

ikevin127 mentioned this pull request Apr 14, 2024

Bank account label in Workspace > Workflows > Make or track payments is too small #40204

Closed

6 tasks

Merge branch 'main' into fix/39947

042e04a

fixed infinite loading while offline

61afb5b

Merge branch 'main' of https://github.com/Expensify/App into fix/39947

0d5b1f2

lakchote added the Ready To Build label May 17, 2024

ishpaul777 reviewed May 17, 2024

View reviewed changes

ikevin127 added 2 commits May 20, 2024 11:36

adjusted offline mode styles and spacing

31bddf5

fixed type error

f4f6931

ishpaul777 approved these changes May 22, 2024

View reviewed changes

melvin-bot bot requested a review from lakchote May 22, 2024 16:10

lakchote previously approved these changes May 22, 2024

View reviewed changes

Merge branch 'main' of https://github.com/Expensify/App into fix/39947

84a1c4a

ikevin127 dismissed lakchote’s stale review via 84a1c4a May 28, 2024 21:09

lakchote approved these changes May 29, 2024

View reviewed changes

lakchote merged commit 1183a92 into Expensify:main May 29, 2024
16 checks passed

github-actions bot mentioned this pull request May 29, 2024

Deploy Checklist: New Expensify 2024-05-29 #42741

Closed

Bank account and Authorized payer buttons displayed instead of Connect bank account #40182

Bank account and Authorized payer buttons displayed instead of Connect bank account #40182

Conversation

ikevin127 commented Apr 12, 2024

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Apr 12, 2024

shawnborton commented Apr 14, 2024

dubielzyk-expensify commented Apr 15, 2024

trjExpensify commented Apr 15, 2024

ikevin127 commented Apr 15, 2024

ishpaul777 commented Apr 16, 2024

ishpaul777 commented Apr 16, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

ishpaul777 commented Apr 16, 2024 • edited Loading

ikevin127 commented Apr 16, 2024

ikevin127 commented Apr 16, 2024

trjExpensify commented Apr 16, 2024

ishpaul777 commented Apr 17, 2024

ikevin127 commented Apr 17, 2024

ishpaul777 commented Apr 17, 2024 • edited Loading

ikevin127 commented Apr 17, 2024 • edited Loading

ishpaul777 commented Apr 20, 2024 • edited Loading

trjExpensify commented May 8, 2024

ikevin127 commented May 8, 2024 • edited Loading

lakchote commented May 9, 2024

trjExpensify commented May 9, 2024

shawnborton commented May 9, 2024

lakchote commented May 17, 2024

github-actions bot commented May 17, 2024

ishpaul777 commented May 17, 2024

ishpaul777 commented May 17, 2024

shawnborton commented May 17, 2024

ishpaul777 commented May 17, 2024

shawnborton commented May 17, 2024

ishpaul777 May 17, 2024 • edited Loading

Choose a reason for hiding this comment

shawnborton May 17, 2024

Choose a reason for hiding this comment

ikevin127 May 17, 2024

Choose a reason for hiding this comment

ishpaul777 May 18, 2024

Choose a reason for hiding this comment

ishpaul777 commented May 17, 2024

shawnborton commented May 17, 2024

ikevin127 commented May 17, 2024

shawnborton commented May 20, 2024

ikevin127 commented May 20, 2024

ishpaul777 left a comment

Choose a reason for hiding this comment

ikevin127 commented May 28, 2024

lakchote commented May 29, 2024

OSBotify commented May 29, 2024

OSBotify commented May 29, 2024

OSBotify commented May 30, 2024

OSBotify commented May 30, 2024

ishpaul777 commented Apr 16, 2024 •

edited

Loading

ishpaul777 commented Apr 16, 2024 •

edited

Loading

ishpaul777 commented Apr 17, 2024 •

edited

Loading

ikevin127 commented Apr 17, 2024 •

edited

Loading

ishpaul777 commented Apr 20, 2024 •

edited

Loading

ikevin127 commented May 8, 2024 •

edited

Loading

ishpaul777 May 17, 2024 •

edited

Loading