Feat: Add a step to to Request Physical Card form that collects a magic code #51135

hungvu193 · 2024-10-20T09:56:04Z

Details

This PR added a validate code modal when user want to issue a physical card.

Fixed Issues

$ #50967
PROPOSAL: N/A

Tests

Prerequisite: Your account needs at least one physical card added.

Go to your Settings => Wallet.
Click on your Physical card => Issue card.
Enter all necessary information => Press Ship card.
Verify that there's modal that allow you to enter magic code.
Enter the magic code.
Verify that you can continue with the flow after that.

Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as Tests.

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

Screen.Recording.2024-11-01.at.14.16.51.mov

MacOS: Desktop

Desskotp.mov

…l' into feat-50967

hungvu193 · 2024-10-20T10:27:47Z

Note: It looks like BE currently doesn't throw errors with invalid validate code.

situchan

hungvu193 · 2024-10-23T07:01:07Z

I see. This is not related to current changes, however I think it's easy to update it so I can include useOnyx migration in this PR

melvin-bot · 2024-10-24T02:07:24Z

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

hungvu193 · 2024-10-24T02:07:44Z

Onyx migration 's done. I mark this PR is ready so the linked issue won't be overdue.

src/types/onyx/Card.ts

hungvu193 · 2024-11-01T04:45:30Z

@NikkiWines What's the successful response? Can you give me the example? I'm seeing here's the error response, it merges requestPhysicalCardForm key.

hungvu193 · 2024-11-01T07:23:16Z

Another thing, The error that's showing between assigned card sections and inside ValidateCodeActionModal are different, do we need to fix it as well?

Screen.Recording.2024-11-01.at.14.17.49.mov

src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx

Co-authored-by: Dominic <[email protected]>

dominictb · 2024-11-12T06:43:41Z

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

Android: mWeb Chrome

iOS: Native

Screen.Recording.2024-11-15.at.11.56.20-compressed.mov

iOS: mWeb Safari

Screen.Recording.2024-11-15.at.11.27.17-compressed.mov

MacOS: Chrome / Safari

Screen.Recording.2024-11-15.at.11.18.41-compressed.mov

MacOS: Desktop

dominictb · 2024-11-12T07:50:57Z

@hungvu193 Are #51135 (comment) and #51135 (comment) expected? Or are we waiting for BE changes?

hungvu193 · 2024-11-12T08:00:21Z

@hungvu193 Are #51135 (comment) and #51135 (comment) expected? Or are we waiting for BE changes?

I think they're expected for now. I believe we don't want to block existing user from using this feature at the moment because we haven't released this PR yet. cc @NikkiWines

src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx

dominictb · 2024-11-12T08:42:49Z

BUG: If I abandoned the verify flow (wrong magic code then close the RHP) and refreshed, the card automatically turned to have NOT_ACTIVATED state

But seems like it's this one #51135 (comment) and a BE bug.

dominictb · 2024-11-12T08:53:07Z

BUG: If I entered wrong validate code, I would always got Card data missing in detail error like #51135 (comment) all the time even when I entered the correct code.

I think it is a BE bug as well.

dominictb · 2024-11-12T09:05:56Z

The above issue ^ together with the rate limit of ResendValidateCode made this PR very difficult to test. I'll try again tonight.

NikkiWines · 2024-11-13T00:20:11Z

@dominictb you might be able to test more easily by following the setup steps from this PR? @hungvu193 it might be helpful to incorporate something like this into the QA steps as well

NikkiWines

Couple of comments

src/components/ValidateCodeActionModal/ValidateCodeForm/BaseValidateCodeForm.tsx

src/components/ValidateCodeActionModal/type.ts

src/libs/actions/Wallet.ts

src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx

hungvu193 · 2024-11-13T04:14:47Z

Couple of comments

Addressed all the comments

NikkiWines · 2024-11-13T21:31:55Z

@hungvu193 you've got conflicts

NikkiWines · 2024-11-14T21:21:49Z

@dominictb can you re-review please 🙇

dominictb · 2024-11-15T04:30:46Z

src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx

+        (validateCode: string) => {
+            setCurrentCardID(cardToBeIssued?.cardID.toString());
+            const updatedPrivatePersonalDetails = GetPhysicalCardUtils.getUpdatedPrivatePersonalDetails(draftValues, privatePersonalDetails);
+            Wallet.requestPhysicalExpensifyCard(cardToBeIssued?.cardID ?? -1, session?.authToken ?? '', updatedPrivatePersonalDetails, validateCode);


I think this is the line causing the -1 problem. I can still reproduce it.

Please retest before requesting another review round.

Sure. I'll do it shortly

We clear the error when modal is hide, unfortunately we used the old cardID value for it, which caused the issue, can you verify it now? Ty

dominictb · 2024-11-15T08:05:14Z

@hungvu193 BUG: If we previously verified code in Get Physical Card flow then verified in Issue New Card Flow, OR VICE VERSA, ResendValidateCode API is not called the first time. It would only be called if we pressed Didn't receive a magic code?.

If we already requested validate code in another flow, validateActionCode.validateCodeSent is true. Later, this line prevents sendValidateCode if hasMagicCodeBeenSent:

App/src/components/ValidateCodeActionModal/index.tsx

Line 45 in 0855d78

if (!firstRenderRef.current || !isVisible || hasMagicCodeBeenSent) {

I think this is somehow related to #51663 but cannot confirm if it's expected (to prevent excessive API calls within a short duration). Can you confirm?

hungvu193 · 2024-11-15T08:07:47Z

Yes, It's to prevent excessive API calls. But I think we should also fix it, we should add optimistic data to our API that use validateCode param.

dominictb · 2024-11-15T08:08:26Z

Thanks. Please do.

NikkiWines · 2024-11-18T23:49:03Z

@hungvu193 what's the latest here, can @dominictb re-review now?

hungvu193 · 2024-11-19T00:03:35Z

@hungvu193 what's the latest here, can @dominictb re-review now?

Yes. I commented here

dominictb · 2024-11-19T01:23:01Z

src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx

+    const [draftValues] = useOnyx(ONYXKEYS.FORMS.GET_PHYSICAL_CARD_FORM_DRAFT);
+    const [account] = useOnyx(ONYXKEYS.ACCOUNT);
+    const [isActionCodeModalVisible, setActionCodeModalVisible] = useState(false);
+    const [formData] = useOnyx(ONYXKEYS.FORMS.REPORT_PHYSICAL_CARD_FORM);
    const domainCards = CardUtils.getDomainCards(cardList)[domain] || [];
    const cardToBeIssued = domainCards.find((card) => !card?.nameValuePairs?.isVirtual && card?.state === CONST.EXPENSIFY_CARD.STATE.STATE_NOT_ISSUED);
    const cardID = cardToBeIssued?.cardID.toString() ?? '-1';


Please remove this intermediary variable and replace all its usages to avoid confusion (e.g., why cardID somewhere and currentCardID elsewhere).

dominictb · 2024-11-19T01:26:13Z

src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx

+        // Current step of the get physical card flow should be the confirmation page; and
+        // Card has NOT_ACTIVATED state when successfully being issued so cardToBeIssued should be undefined
+        // -1 is not a valid cardID, we don't need to clean up the form value in that case.
+        if (!isConfirmation || !!cardToBeIssued || !currentCardID || currentCardID === '-1') {


If so, do we still need currentCardID === '-1'?

dominictb · 2024-11-19T01:28:05Z

src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx

+        // so that no stale data is left on Onyx
+        FormActions.clearDraftValues(ONYXKEYS.FORMS.GET_PHYSICAL_CARD_FORM);
+        Wallet.clearPhysicalCardError(currentCardID);
+        Navigation.navigate(ROUTES.SETTINGS_WALLET_DOMAINCARD.getRoute(currentCardID.toString()));


Suggested change

Navigation.navigate(ROUTES.SETTINGS_WALLET_DOMAINCARD.getRoute(currentCardID.toString()));

Navigation.navigate(ROUTES.SETTINGS_WALLET_DOMAINCARD.getRoute(currentCardID));

dominictb · 2024-11-19T01:28:29Z

Please also merge main.

hungvu193 added 2 commits October 20, 2024 16:19

Merge remote-tracking branch 'getusha/reuse-validate-code-action-moda…

f001f00

…l' into feat-50967

Add validatecode modal when issuing Physical card

6aa9281

hungvu193 mentioned this pull request Oct 20, 2024

Add a step to to Request Physical Card form that collects a magic code #50967

Open

adjust logic

b1e52cc

hungvu193 added 3 commits October 20, 2024 17:29

address linting

2d1a57b

revert .ruby-version

91bc9b1

merge main

6eeabd4

situchan suggested changes Oct 23, 2024

View reviewed changes

Onyx migration

9890494

hungvu193 marked this pull request as ready for review October 24, 2024 02:07

hungvu193 requested a review from a team as a code owner October 24, 2024 02:07

melvin-bot bot requested a review from situchan October 24, 2024 02:07

melvin-bot bot removed the request for review from a team October 24, 2024 02:07

hungvu193 changed the title ~~Feat: Add a step to to Request Physical Card form that collects a magic code~~ [Hold for BE PR] Feat: Add a step to to Request Physical Card form that collects a magic code Oct 25, 2024

hungvu193 added 2 commits October 30, 2024 14:28

Merge remote-tracking branch 'origin/main' into feat-50967

60a5c2a

handle generic error

55187f4

NikkiWines requested changes Oct 31, 2024

View reviewed changes

src/types/onyx/Card.ts Outdated Show resolved Hide resolved

hungvu193 added 2 commits November 1, 2024 10:08

update the error field

340d3b1

Merge remote-tracking branch 'origin/main' into feat-50967

d4eb736

add loading field and other stuffs

23c5163

hungvu193 changed the title ~~[Hold for BE PR] Feat: Add a step to to Request Physical Card form that collects a magic code~~ Feat: Add a step to to Request Physical Card form that collects a magic code Nov 1, 2024

remove cardState optimistic

6ce22aa

hungvu193 added 2 commits November 1, 2024 14:36

prettier

2224d58

fix lint

60d0fdc

dominictb suggested changes Nov 12, 2024

View reviewed changes

src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx Outdated Show resolved Hide resolved

src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx Outdated Show resolved Hide resolved

hungvu193 and others added 2 commits November 12, 2024 10:11

Update src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx

982abf0

Co-authored-by: Dominic <[email protected]>

Update src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx

55c4a0c

Co-authored-by: Dominic <[email protected]>

This comment was marked as resolved.

Sign in to view

dominictb reviewed Nov 12, 2024

View reviewed changes

src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx Show resolved Hide resolved

NikkiWines requested changes Nov 13, 2024

View reviewed changes

address comment

cbf6a2b

hungvu193 added 4 commits November 14, 2024 17:40

merge main

58c2b39

remove dupe props

0855d78

deprecate description props

5c75531

address comment

fb7ee30

dominictb suggested changes Nov 15, 2024

View reviewed changes

fix -1 value appears inside cardList

ceca20c

dominictb suggested changes Nov 19, 2024

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Feat: Add a step to to Request Physical Card form that collects a magic code #51135

Feat: Add a step to to Request Physical Card form that collects a magic code #51135

hungvu193 commented Oct 20, 2024 •

edited

Loading

hungvu193 commented Oct 20, 2024

situchan left a comment

hungvu193 commented Oct 23, 2024

melvin-bot bot commented Oct 24, 2024

hungvu193 commented Oct 24, 2024 •

edited

Loading

hungvu193 commented Nov 1, 2024

hungvu193 commented Nov 1, 2024

dominictb commented Nov 12, 2024 •

edited

Loading

dominictb commented Nov 12, 2024 •

edited

Loading

hungvu193 commented Nov 12, 2024

This comment was marked as resolved.

dominictb commented Nov 12, 2024

dominictb commented Nov 12, 2024

dominictb commented Nov 12, 2024

NikkiWines commented Nov 13, 2024 •

edited

Loading

NikkiWines left a comment

hungvu193 commented Nov 13, 2024

NikkiWines commented Nov 13, 2024

NikkiWines commented Nov 14, 2024

dominictb Nov 15, 2024

dominictb Nov 15, 2024

hungvu193 Nov 15, 2024

hungvu193 Nov 15, 2024

dominictb commented Nov 15, 2024 •

edited

Loading

hungvu193 commented Nov 15, 2024

dominictb commented Nov 15, 2024

NikkiWines commented Nov 18, 2024

hungvu193 commented Nov 19, 2024

dominictb Nov 19, 2024

dominictb Nov 19, 2024

dominictb Nov 19, 2024

dominictb commented Nov 19, 2024

	Navigation.navigate(ROUTES.SETTINGS_WALLET_DOMAINCARD.getRoute(currentCardID.toString()));
	Navigation.navigate(ROUTES.SETTINGS_WALLET_DOMAINCARD.getRoute(currentCardID));

Feat: Add a step to to Request Physical Card form that collects a magic code #51135

Are you sure you want to change the base?

Feat: Add a step to to Request Physical Card form that collects a magic code #51135

Conversation

hungvu193 commented Oct 20, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

hungvu193 commented Oct 20, 2024

situchan left a comment

Choose a reason for hiding this comment

hungvu193 commented Oct 23, 2024

melvin-bot bot commented Oct 24, 2024

hungvu193 commented Oct 24, 2024 • edited Loading

hungvu193 commented Nov 1, 2024

hungvu193 commented Nov 1, 2024

dominictb commented Nov 12, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

dominictb commented Nov 12, 2024 • edited Loading

hungvu193 commented Nov 12, 2024

This comment was marked as resolved.

dominictb commented Nov 12, 2024

dominictb commented Nov 12, 2024

dominictb commented Nov 12, 2024

NikkiWines commented Nov 13, 2024 • edited Loading

NikkiWines left a comment

Choose a reason for hiding this comment

hungvu193 commented Nov 13, 2024

NikkiWines commented Nov 13, 2024

NikkiWines commented Nov 14, 2024

dominictb Nov 15, 2024

Choose a reason for hiding this comment

dominictb Nov 15, 2024

Choose a reason for hiding this comment

hungvu193 Nov 15, 2024

Choose a reason for hiding this comment

hungvu193 Nov 15, 2024

Choose a reason for hiding this comment

dominictb commented Nov 15, 2024 • edited Loading

hungvu193 commented Nov 15, 2024

dominictb commented Nov 15, 2024

NikkiWines commented Nov 18, 2024

hungvu193 commented Nov 19, 2024

dominictb Nov 19, 2024

Choose a reason for hiding this comment

dominictb Nov 19, 2024

Choose a reason for hiding this comment

dominictb Nov 19, 2024

Choose a reason for hiding this comment

dominictb commented Nov 19, 2024

hungvu193 commented Oct 20, 2024 •

edited

Loading

hungvu193 commented Oct 24, 2024 •

edited

Loading

dominictb commented Nov 12, 2024 •

edited

Loading

dominictb commented Nov 12, 2024 •

edited

Loading

NikkiWines commented Nov 13, 2024 •

edited

Loading

dominictb commented Nov 15, 2024 •

edited

Loading