Add workspace upgrade flow #43822

allroundexperts · 2024-06-17T10:14:26Z

Details

This PR adds ability to upgrade the workspace to corporate plan.

Fixed Issues

$ #43916

Tests

Open workspace settings page and add upgrade/report-fields to the url. (eg settings/workspaces/670843E4FAC26E3A/upgrade/report-fields)
Verify that the upgrade page appears as per the designs.

Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Open workspace settings page and add upgrade/report-fields to the url. (eg settings/workspaces/670843E4FAC26E3A/upgrade/report-fields)
Verify that the upgrade page appears as per the designs.

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: mWeb Chrome
- iOS: Native
- iOS: mWeb 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 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 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 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.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

youssef-lr · 2024-06-26T18:33:19Z

src/libs/actions/Policy/Policy.ts

+            onyxMethod: Onyx.METHOD.MERGE,
+            key: `policy_${policyID}`,
+            value: {
+                isPendingUpgrade: true,


let's add these optimistic values and their keys in CONST if they're not there:

type=CORPORATE maxExpenseAge=CONST.POLICY.DEFAULT_MAX_EXPENSE_AGE=90 maxExpenseAmount=CONST.POLICY.DEFAULT_MAX_EXPENSE_AMOUNT=200000 maxExpenseAmountNoReceipt=CONST.POLICY.DEFAULT_MAX_AMOUNT_NO_RECEIPT=2500 glCodes=true

And then add these values to the optimistic data if instant submit is enabled:

if (isInstantSubmitEnabled(policy)) { // set autoReporting=false // set autoReportingFrequency=CONST.POLICY.AUTO_REPORTING_FREQUENCIES.MANUAL }

…ns-fixButtonWidthDisableTaxSorting

melvin-bot · 2024-06-27T21:25:07Z

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

ishpaul777 · 2024-06-27T21:27:35Z

I assume this needs a c+ review ?

allroundexperts · 2024-06-27T21:49:51Z

I assume this needs a c+ review ?

Yes.

ishpaul777 · 2024-06-27T22:13:49Z

Okay thanks for clarifying, i'll get this done, when i start tomorrow. 😄

ishpaul777 · 2024-06-28T14:38:36Z

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-07-02-01-27-57.mp4

Android: mWeb Chrome

Record_2024-07-02-01-37-13.mp4

iOS: Native

Screen.Recording.2024-07-01.at.3.05.38.AM.mov

iOS: mWeb Safari

Screen.Recording.2024-07-01.at.3.22.28.AM.mov

MacOS: Chrome / Safari

Screen.Recording.2024-07-01.at.2.49.21.AM.mov

MacOS: Desktop

Screen.Recording.2024-07-01.at.4.04.00.AM.mov

ishpaul777 · 2024-06-28T14:39:21Z

@allroundexperts There are prettier diffs

ishpaul777

Looks great! just some minor comments

src/libs/actions/Policy/Policy.ts

src/pages/workspace/upgrade/UpgradeConfirmation.tsx

src/pages/workspace/upgrade/UpgradeIntro.tsx

src/pages/workspace/upgrade/WorkspaceUpgradePage.tsx

src/languages/es.ts

garrettmknight · 2024-07-01T15:13:39Z

Translations are here: https://docs.google.com/document/d/1nSWknL5X-Rh_yX0caTSbQQJ4mT8N5D3dzZC9WQg0O9o/edit?usp=sharing

…ns-fixButtonWidthDisableTaxSorting

shawnborton · 2024-07-03T10:57:53Z

For this particular report fields upgrade screen, I don't think we're using the correct illustration:

It should match what we have in More features:

shawnborton · 2024-07-03T10:59:17Z

And to clarify, is Report Fields the only upgrade screen at the moment, or are there others I should/can review as well? Thanks!

github-actions · 2024-07-03T11:25:45Z

🧪🧪 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/43822/index.html	❌ FAILED ❌
	The QR code can't be generated, because the iOS build failed
Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/43822/NewExpensify.dmg	https://43822.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

garrettmknight · 2024-07-03T11:59:22Z

@shawnborton I think we should have NetSuite and Intacct ready for review this week, too, but they're not ready yet.

shawnborton · 2024-07-03T13:05:16Z

I think we want to be using our large button size here, can you update that as well? Right now it looks just slightly too small:

shawnborton · 2024-07-03T13:06:20Z

Also @garrettmknight is that the copy we settled on for report fields? Feels a bit short - I was thinking we could use it as an opportunity to sell the feature a bit. We also don't have any indication of price or anything here, which I could have sworn we did from the mocks.

allroundexperts · 2024-07-03T15:47:11Z

@shawnborton Handled all your comments and updated the copy. Please review the following.

shawnborton · 2024-07-03T15:50:10Z

Wonderful, thanks!

ishpaul777 · 2024-07-03T16:52:38Z

we have conflicts @allroundexperts

ishpaul777 · 2024-07-03T18:28:13Z

src/pages/workspace/upgrade/UpgradeIntro.tsx

+    const {translate} = useLocalize();
+
+    return (
+        <View style={styles.p5}>


Sorry for not noticing this before but we do have a Section component can we reuse it here @allroundexperts

Can you provide the full name of this component?

https://github.com/Expensify/App/blob/bdd0adc6e2b86741f8d8294b835003839df53c04/src/components/Section/index.tsx

Hm... Would this be plug in play? I think we'll need to do some changes within this component to meet our needs.

Hm... Would this be plug in play? I think we'll need to do some changes within this component to meet our needs.

Ideally we should reuse but we def. need to make changes to component to meet our needs here, I dont think this is super important change, current component is readable as it is. Consider this as a optional comment 👍

youssef-lr

LGTM!

OSBotify · 2024-07-05T18:57:35Z

✋ 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-07-08T09:57:28Z

🚀 Deployed to staging by https://github.com/youssef-lr in version: 9.0.5-0 🚀

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

OSBotify · 2024-07-08T10:53:48Z

🚀 Deployed to staging by https://github.com/youssef-lr in version: 9.0.5-2 🚀

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

OSBotify · 2024-07-10T10:56:38Z

🚀 Deployed to production by https://github.com/Julesssss in version: 9.0.5-13 🚀

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

OSBotify · 2024-07-15T20:19:02Z

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

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

ahmedGaber93 · 2025-01-13T11:37:12Z

src/languages/en.ts

+                description: `Report fields let you specify header-level details, distinct from tags that pertain to expenses on individual line items. These details can encompass specific project names, business trip information, locations, and more.`,
+                pricing: {
+                    onlyAvailableOnPlan: 'Report fields are only available on the Control plan, starting at ',
+                    amount: '$9 ',


Coming from #53878, the upgrade price is not displayed in local currency and always displayed in USD, and we fix it here #54340.

dukenv0307 · 2025-01-16T03:09:48Z

src/CONST.ts

@@ -791,6 +791,7 @@ const CONST = {
                    UPDATE_TIME_ENABLED: 'POLICYCHANGELOG_UPDATE_TIME_ENABLED',
                    UPDATE_TIME_RATE: 'POLICYCHANGELOG_UPDATE_TIME_RATE',
                    LEAVE_POLICY: 'POLICYCHANGELOG_LEAVE_POLICY',
+                    CORPORATE_UPGRADE: 'POLICYCHANGELOG_CORPORATE_UPGRADE',


Coming from #54397. We should translate the system message for POLICYCHANGELOG_CORPORATE_UPGRADE.

fedirjh · 2025-01-17T14:44:34Z

src/libs/actions/Policy/Policy.ts

+                ...(PolicyUtils.isInstantSubmitEnabled(policy) && {
+                    autoReporting: true,
+                    autoReportingFrequency: CONST.POLICY.AUTO_REPORTING_FREQUENCIES.MANUAL,
+                }),


Coming from #54040, When we upgrade to corp, the backend sets autoReportingFrequency to Instant. more context in #54040

allroundexperts added 3 commits June 17, 2024 14:17

add workspace upgrade flow

dcebd22

add offline indicator

5bc393b

fix lint errors

63ba1f8

youssef-lr self-requested a review June 26, 2024 16:44

youssef-lr reviewed Jun 26, 2024

View reviewed changes

allroundexperts added 4 commits June 27, 2024 19:10

WIP: 1777d7e Merge pull request Expensify#43140 from Expensify/cmarti…

a9695dc

…ns-fixButtonWidthDisableTaxSorting

handle comments

17e4cab

prettier fix

1e36d4e

Merge branch 'main' into feat-workspace-upgrade

ce28f3a

allroundexperts marked this pull request as ready for review June 27, 2024 21:25

allroundexperts requested review from a team as code owners June 27, 2024 21:25

melvin-bot bot removed the request for review from a team June 27, 2024 21:25

melvin-bot bot requested a review from ishpaul777 June 27, 2024 21:25

fix: broken desktop build

0e7c440

ishpaul777 reviewed Jun 28, 2024

View reviewed changes

allroundexperts added 3 commits June 30, 2024 19:59

merge with main

21bbbc8

prettier fix

7113174

handle comments

f38856b

allroundexperts requested review from ishpaul777 and youssef-lr June 30, 2024 15:45

ishpaul777 reviewed Jun 30, 2024

View reviewed changes

src/languages/es.ts Outdated Show resolved Hide resolved

WIP: 1777d7e Merge pull request Expensify#43140 from Expensify/cmarti…

9b01337

…ns-fixButtonWidthDisableTaxSorting

shawnborton added the Ready To Build label Jul 3, 2024

allroundexperts added 2 commits July 3, 2024 19:56

Merge branch 'main' into feat-workspace-upgrade

e95b10b

handle comments

df8d035

ishpaul777 reviewed Jul 3, 2024

View reviewed changes

allroundexperts added 2 commits July 4, 2024 00:48

Merge branch 'main' into feat-workspace-upgrade

c8bac1f

Update CONST.ts

d05ccd7

youssef-lr approved these changes Jul 5, 2024

View reviewed changes

youssef-lr merged commit 3a2de49 into Expensify:main Jul 5, 2024
14 checks passed

github-actions bot mentioned this pull request Jul 8, 2024

Deploy Checklist: New Expensify 2024-07-08 #44947

Closed

86 tasks

lanitochka17 mentioned this pull request Jul 8, 2024

Workspace - The price $9 in upgrade page is not legible in light mode #44965

Closed

6 tasks

m-natarajan mentioned this pull request Jul 8, 2024

[HOLD for payment 2024-07-25] Android - Workspace upgrade - Offline indicator is below the content #44971

Closed

6 tasks

melvin-bot bot mentioned this pull request Jul 10, 2024

[HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [Upgrades] Create Upgrade RHN Panel, Confirmation Panel and connect to upgradeToCorporate action + apply to Report Fields #43916

Closed

ahmedGaber93 reviewed Jan 13, 2025

View reviewed changes

dukenv0307 reviewed Jan 16, 2025

View reviewed changes

fedirjh reviewed Jan 17, 2025

View reviewed changes

fedirjh mentioned this pull request Jan 17, 2025

[HOLD for payment 2025-01-21] [HOLD for payment 2025-01-18] [$250] Workflows -"Delay submissions" is auto-enabled after upgrading workspace and then auto-disabled #54040

Closed

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add workspace upgrade flow #43822

Add workspace upgrade flow #43822

allroundexperts commented Jun 17, 2024 •

edited

Loading

youssef-lr Jun 26, 2024 •

edited

Loading

allroundexperts Jun 27, 2024

melvin-bot bot commented Jun 27, 2024

ishpaul777 commented Jun 27, 2024

allroundexperts commented Jun 27, 2024

ishpaul777 commented Jun 27, 2024 •

edited

Loading

ishpaul777 commented Jun 28, 2024 •

edited

Loading

ishpaul777 commented Jun 28, 2024

ishpaul777 left a comment

garrettmknight commented Jul 1, 2024

shawnborton commented Jul 3, 2024

shawnborton commented Jul 3, 2024

github-actions bot commented Jul 3, 2024

garrettmknight commented Jul 3, 2024

shawnborton commented Jul 3, 2024

shawnborton commented Jul 3, 2024

allroundexperts commented Jul 3, 2024

shawnborton commented Jul 3, 2024

ishpaul777 commented Jul 3, 2024

ishpaul777 Jul 3, 2024

allroundexperts Jul 3, 2024

ishpaul777 Jul 3, 2024

allroundexperts Jul 3, 2024

ishpaul777 Jul 3, 2024

youssef-lr left a comment

OSBotify commented Jul 5, 2024

OSBotify commented Jul 8, 2024

OSBotify commented Jul 8, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 15, 2024

ahmedGaber93 Jan 13, 2025

dukenv0307 Jan 16, 2025

fedirjh Jan 17, 2025

Add workspace upgrade flow #43822

Add workspace upgrade flow #43822

Conversation

allroundexperts commented Jun 17, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

youssef-lr Jun 26, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

melvin-bot bot commented Jun 27, 2024

ishpaul777 commented Jun 27, 2024

allroundexperts commented Jun 27, 2024

ishpaul777 commented Jun 27, 2024 • edited Loading

ishpaul777 commented Jun 28, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

ishpaul777 commented Jun 28, 2024

ishpaul777 left a comment

Choose a reason for hiding this comment

garrettmknight commented Jul 1, 2024

shawnborton commented Jul 3, 2024

shawnborton commented Jul 3, 2024

github-actions bot commented Jul 3, 2024

garrettmknight commented Jul 3, 2024

shawnborton commented Jul 3, 2024

shawnborton commented Jul 3, 2024

allroundexperts commented Jul 3, 2024

shawnborton commented Jul 3, 2024

ishpaul777 commented Jul 3, 2024

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

youssef-lr left a comment

Choose a reason for hiding this comment

OSBotify commented Jul 5, 2024

OSBotify commented Jul 8, 2024

OSBotify commented Jul 8, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 15, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

allroundexperts commented Jun 17, 2024 •

edited

Loading

youssef-lr Jun 26, 2024 •

edited

Loading

ishpaul777 commented Jun 27, 2024 •

edited

Loading

ishpaul777 commented Jun 28, 2024 •

edited

Loading