Create a group chat info view with participants information. #2178

npsedhain · 2021-03-31T20:42:53Z

Details

Added a modal view to show the list of all the participants in the group chat.

Fixed Issues

Fixes GH_LINK_ISSUE_2105

Tests

Go to a group chat page.
Click on the title bar with the participants' names.
A modal with the participants' information appears.
On clicking each of the participants, the details page with each participant's information is displayed.

Tested On

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Luke9389

Hello! This is looking great! Thanks for your contribution. I've left some comments here, some little stuff, some questions (I'm not too familiar with this part of our codebase), and some other stylistic ideas. I'm gonna go ahead and request another reviewer for redundancy.

src/pages/ParticipantsPage.js

Luke9389 · 2021-04-01T00:19:16Z

src/pages/ParticipantsPage.js

+        },
+    ];
+
+    return final.map(item => ({...item, participantsList: [item]}));


Why are we adding the participantsList key?

The OptionsList component seems to use the text to display from within the participantsList key. It was pretty weird for me too, but it threw error without it.

Hey @npsedhain thanks for your patience while I was looking into this. Here were my concerns:

We're sending two copies of the same data, nested in itself

We're putting a single object into an array just to satisfy a proptype rule

These two concerns acted as a red flag for me, indicating that we were holding something wrong.

I started my investigation by looking at the other place in which OptionsList is used. The items that are usually in sections.data are not single people but whole reports (chats). While Options list looks like the correct component for the job, it was actually written with a different purpose in mind.

Two potential avenues forward:

Don't worry about it. It works so whatever.

Write a component that's actually meant for this.

To help us suss this out, I'd like to include @marcaaron in this decision. He wrote much of OptionsList and is very knowledgeable in the codebase.

Thanks, @Luke9389, I will the changes as suggested by @marcaaron, i.e., only sending the two keys needed.

src/pages/ParticipantsPage.js

npsedhain · 2021-04-01T06:29:11Z

@Luke9389, I have pushed the recommended changes. Please feel free to go through it again and let me know if you have any more suggestions!

Luke9389 · 2021-04-01T21:08:04Z

Will do, thanks @npsedhain

NikkiWines

This is looking good. Agreed with @Luke9389 that the duplicated participantsList is pretty weird and should be modified.

Also, just a note that the report view disappears from the background when navigating from the participants page to the details page, which isn't ideal.

Screen.Recording.2021-04-01.at.4.30.04.PM.mov

NikkiWines · 2021-04-01T21:47:18Z

src/pages/ParticipantsPage.js

+    const {icons, participants, reportName} = report;
+    const displayNames = reportName.split(', ');
+
+    const members = participants.reduce((list, login, idx) => {


I believe we prefer to use non-abbreviated variable names wherever possible so idx should be index

@NikkiWines, regarding the report view disappearing when navigating to the details page, I found it to be a little weird as well. But when I navigated across the application, it occurred to me that it was an existing problem. I can take a look at what exactly is causing that issue.
For example, also happens in the route /iou/request

NikkiWines · 2021-04-01T23:04:23Z

src/libs/Navigation/linkingConfig.js

@@ -67,6 +67,12 @@ export default {
                    Details_Root: ROUTES.DETAILS_WITH_LOGIN,
                },
            },
+            Participants: {
+                initialRouteName: 'Participants_Root',


Is there a reason for initialRouteName here?

I don't think it's required as well, thanks for pointing it out.

trjExpensify · 2021-04-02T00:12:54Z

👋 Couple of thoughts:

Is there a reason why we aren't letting a user navigate back to the participant list, after they go a level deeper to the individual profile view? Forcing a user to close the modal and reopen it to go back seems sub-optimal, so I'd suggest we add a < caret to allow for a user to go back.
We're using Participants as the header title. This should be Details as per the supplied mock, right?

(Granted, when we add more settings/functionality to the Details side modal in the future, we may have a sub-page for the participants list, but even then my vote would be to refer to them as Members as that's a bit more consumer-friendly).

marcaaron

I can’t comment on the thread below for some reason to respond to @Luke9389 but to answer the questions...

This is the correct component to use for this and we should not write a new one.
The participantsList thing definitely looks weird / not ideal and I traced this back to this PR…
https://github.com/Expensify/Expensify.cash/pull/1632/files#r594612327

It probably doesn't matter that much that we have some weird data nesting going on here. It doesn't make much sense to me, but I don't see it hurting anything. It's used here to create tooltips which I'm assuming we will also want here for consistency.

https://github.com/Expensify/Expensify.cash/blob/106c52b2410bfab984b8cc7ba786fd2affcc29aa/src/pages/home/sidebar/OptionRowTitle/index.js#L89-L105

So if we want to lean this out a bit we can pass only [{login, displayName}] here instead.

src/libs/Navigation/AppNavigator/ModalStackNavigators.js

marcaaron · 2021-04-02T01:50:41Z

src/pages/ParticipantsPage.js

+    }).isRequired,
+
+    // The chat priority mode
+    priorityMode: PropTypes.string.isRequired,


Hmm I don't think we need to know this...

marcaaron · 2021-04-02T01:53:48Z

src/pages/ParticipantsPage.js

+    },
+    reports: {
+        key: ONYXKEYS.COLLECTION.REPORT,
+    },


We only need to subscribe to a single report here's an example of where we do that

https://github.com/Expensify/Expensify.cash/blob/106c52b2410bfab984b8cc7ba786fd2affcc29aa/src/pages/home/report/ReportActionsView.js#L392-L394

The function can access props in it's argument so you can pull off the reportID via the route.

Thank you for helping, will refactor this one to listen to a single report.

marcaaron · 2021-04-02T01:55:00Z

src/pages/ParticipantsPage.js

+                        hideSectionHeaders
+                        showTitleTooltip
+                        disableFocusOptions
+                        optionMode={priorityMode === CONST.PRIORITY_MODE.GSD ? 'compact' : 'default'}


This is really only relevant in the side bar and can maybe just be set to 'default' here to help simplify things.

marcaaron · 2021-04-02T01:57:10Z

src/pages/ParticipantsPage.js

+        alternateText: personalDetail.login,
+        keyForList: `${participants.length}`,
+        tooltipText: personalDetail.login,
+        displayName: personalDetail.displayName,


I think we can take this out and everything about myPersonalDetails. There's really no need to include the current user here because:

They know already that they're a participant in the chat

They should be accessing their profile via settings

@marcaaron, I looked at a couple of chat applications and found them to have the individual's information listed there too. I can totally remove it if that's not something we want it in here.

marcaaron · 2021-04-02T02:03:26Z

src/pages/ParticipantsPage.js

+    const members = participants.reduce((list, login, idx) => {
+        list.push({
+            alternateText: login,
+            displayName: displayNames[idx],


This works, but it's not really the correct way to access these display names and will break in a future where report names are not structured as they are today.

Instead we should subscribe to the personalDetails key. Then grab everything we need like this:

const userPersonalDetails = props.personalDetails[login]; const displayName = userPersonalDetails.displayName; const avatar = userPersonalDetails.avatar;

etc.

Thank you for the suggestion, will make the change.

marcaaron · 2021-04-02T02:04:29Z

src/pages/ParticipantsPage.js

+    const {icons, participants, reportName} = report;
+    const displayNames = reportName.split(', ');
+
+    const members = participants.reduce((list, login, idx) => {


We use _.reduce() and _.map() etc for consistency.

marcaaron · 2021-04-02T02:05:49Z

src/pages/ParticipantsPage.js

+            <View
+                pointerEvents="box-none"
+                style={[
+                    styles.detailsPageContainer,


Rather than use a page container style that belongs to another page (DetailsPage) we should make this style more generic so it makes sense to use in both contexts.

marcaaron · 2021-04-02T02:06:03Z

src/pages/ParticipantsPage.js

+                    styles.detailsPageContainer,
+                ]}
+            >
+                { participants.length


There's an empty space here before participants

marcaaron · 2021-04-02T02:08:21Z

src/pages/home/HeaderView.js

@@ -83,6 +83,9 @@ const HeaderView = (props) => {
                                if (participants.length === 1) {
                                    Navigation.navigate(ROUTES.getDetailsRoute(participants[0]));
                                }
+                                if (participants.length > 1) {


Rather than check if participants.length > 1 we can just return early when the length === 1 then in all other cases navigate to the new view.

npsedhain · 2021-04-06T03:37:12Z

@marcaaron, I have implemented the details page navigation as per your suggestion. Let me know if you have any concerns. This should solve the issue of the details page exiting the stack which used to make the report page disappear.

cc: @trjExpensify @NikkiWines

Screen.Recording.2021-04-06.at.9.17.45.AM.mov

marcaaron · 2021-04-06T21:11:24Z

@npsedhain Thanks, but it's strange that we cannot go back to view the full list again? We should add a < in the top left corner so we can navigate back to the large list of users. cc @trjExpensify to confirm.

trjExpensify · 2021-04-06T21:20:09Z

Yep, I agree we should add a < to the top left of that screen. 👍

marcaaron

Just a few more comments on this one. Looking better :)

marcaaron · 2021-04-06T21:15:11Z

src/libs/Navigation/AppNavigator/ModalStackNavigators.js

+        <DetailsModalStack.Screen
+            name="Details_Root"
+            headerShown={false}
+            path={ROUTES.REPORT_ID}


Don't think we need this.

marcaaron · 2021-04-06T21:17:13Z

src/libs/Navigation/AppNavigator/ModalStackNavigators.js

+            component={DetailsPage}
+            options={{
+                ...defaultSubRouteOptions,
+                title: 'ParticipantsParticipant',


This will show in a browser tab as ParticipantsParticipant since title sets this text as the webpage title.

Perhaps a better format would be

Report > Participants > {display name of participant}

But I'm not sure we need to figure this out right now and can maybe just leave out the title entirely.

marcaaron · 2021-04-06T21:17:36Z

src/libs/Navigation/AppNavigator/ModalStackNavigators.js

@@ -79,6 +81,31 @@ const DetailsModalStackNavigator = () => (
    </DetailsModalStack.Navigator>
 );

+const ParticipantsModalStackNavigator = () => (
+    <ParticipantsModalStack.Navigator
+        path={ROUTES.PARTICIPANTS}


Pretty sure these path props are not doing anything and the "path" concept is left over from something we have since removed.

marcaaron · 2021-04-06T21:17:53Z

src/ROUTES.js

+    PARTICIPANTS: 'participants',
+    PARTICIPANTS_WITH_REPORT: 'participants/:reportID',
+    getParticipantsRoute: reportID => `participants/${reportID}`,
+    REPORT_ID: '/:reportID',


This doesn't seem like any route we are using...

Yeah the path prop didn't seem to help out there. Will remove this. Thanks for pointing out.

marcaaron · 2021-04-06T21:21:24Z

src/ROUTES.js

+    getParticipantsRoute: reportID => `participants/${reportID}`,
+    REPORT_ID: '/:reportID',
+    PARTICIPANTS_PARTICIPANT_DETAIL: '/participants/:reportID/:login',
+    getParticipantsPartipantDetail: (reportID, login) => `/participants/${reportID}/${login}`,


"participants participant detail" could be more descriptive... e.g. maybe should be REPORT_PARTICIPANTS and REPORT_PARTICIPANT.

As for the routes, is there any reason we can't make these routes...

/r/:reportID/participants

/r/:reportID/participants/:login

?

Yup we can do this, thanks for the suggestion.

marcaaron · 2021-04-06T21:22:19Z

src/libs/Navigation/AppNavigator/AuthScreens.js

@@ -34,6 +34,7 @@ import {
    IOUBillStackNavigator,
    IOURequestModalStackNavigator,
    DetailsModalStackNavigator,
+    ParticipantsModalStackNavigator,


I'd update all instances of Participants* to ReportParticipants so that it's clearer what we are dealing with.

marcaaron · 2021-04-06T21:24:50Z

src/libs/Navigation/AppNavigator/ModalStackNavigators.js

+            name="Participants_Root"
+            component={ParticipantsPage}
+            options={{
+                ...defaultSubRouteOptions,


We should be able to pass these to the navigator instead and prevent having to add this stuff to every screen.

marcaaron · 2021-04-06T21:27:46Z

There are some conflicts here as well that need to be resolved before we can merge this.

Luke9389 · 2021-04-06T21:37:51Z

Regarding the < to go back, we do have an Icon, BackArrow that will work well for this.

marcaaron · 2021-04-06T22:29:17Z

@Luke9389 pretty sure this is built into the header component already https://github.com/Expensify/Expensify.cash/blob/b6d7d60e0d59c68ddf16f1c437033c77f6c8f9e7/src/components/HeaderWithCloseButton.js#L24-L25

Just want to make sure we are not reimplementing behavior we already have, thanks!

npsedhain · 2021-04-07T13:22:25Z

@marcaaron Thanks for the feedbacks, will implement the changes first thing tomorrow and will let you know.

…ubscriptions.

npsedhain · 2021-04-08T16:09:37Z

@marcaaron I have made all the recommended changes, let me know if there is anything else.

marcaaron

Just have a few more minor comments. Looks really nice!

marcaaron · 2021-04-09T01:50:24Z

.github/actions/checkDeployBlockers/index.js

@@ -82,8 +82,6 @@ module.exports = run;

 const _ = __nccwpck_require__(4987);


Doesn't seem like these files are supposed to be here...?

I actually didn't add this. Seem to have been added by @deetergp, a week ago in another PR!

Most likely you merged in the main branch and didn't fix conflicts correctly. Regardless, this file should not be showing with changes in this PR and will need to be fixed before merging.

marcaaron · 2021-04-09T01:52:09Z

src/libs/Navigation/AppNavigator/ModalStackNavigators.js

+        />
+        <DetailsModalStack.Screen
+            name="Details_Root"
+            headerShown={false}


Not necessary because this was passed to navigator screenOptions already?

marcaaron · 2021-04-09T01:54:10Z

src/libs/Navigation/linkingConfig.js

+            Participants: {
+                screens: {
+                    Participants_Root: ROUTES.REPORT_PARTICIPANTS,
+                    Details_Root: ROUTES.REPORT_PARTICIPANT,


not a blocker but this should probably be Participants_Details to follow a similar convention as the settings modal.

Ok now it is a blocker because I think we cannot have Details_Root existing in two navigators? Can we change this to:

ReportParticipants_Root
ReportParticipants_Details

marcaaron · 2021-04-09T01:59:02Z

src/pages/DetailsPage.js

@@ -38,11 +38,13 @@ const DetailsPage = ({personalDetails, route}) => {
            <HeaderWithCloseButton
                title="Details"
                onCloseButtonPress={Navigation.dismissModal}
+                shouldShowBackButton


I think this need a conditional. We don't want to show a back button when there is no modal screen to go back e.g. when there's only one participant

marcaaron · 2021-04-09T02:01:10Z

src/pages/ReportParticipantsPage.js

+ * Returns all the participants in the active report
+ *
+ * @param {Object} report The active report object
+ * @param {Array} personalDetails The personal details of the users


This is an Object.

NikkiWines

Couple of comments but overall really coming together

NikkiWines · 2021-04-09T02:50:08Z

src/pages/ReportParticipantsPage.js

+const propTypes = {
+    /* Onyx Props */
+    // The personal details of the person who is logged in
+    personalDetails: PropTypes.shape({


We have personalDetailsPropType.js which you can import instead of redefining the props here.

src/pages/ReportParticipantsPage.js

npsedhain · 2021-04-11T10:15:21Z

I have pushed changes including all the recent comments. Please, do let me know if there is more.
cc: @marcaaron @NikkiWines

marcaaron · 2021-04-12T15:46:53Z

.github/actions/checkDeployBlockers/index.js

@@ -82,8 +82,6 @@ module.exports = run;

 const _ = __nccwpck_require__(4987);


Most likely you merged in the main branch and didn't fix conflicts correctly. Regardless, this file should not be showing with changes in this PR and will need to be fixed before merging.

NikkiWines

Aside from the modifications to the .github/ files, this is looking good. Had one minor question about using login vs userLogin

NikkiWines · 2021-04-12T20:47:55Z

src/pages/ReportParticipantsPage.js

+            alternateText: userLogin,
+            displayName: userPersonalDetail.displayName,
+            icons: [userPersonalDetail.avatar],
+            keyForList: login,


is there a reason to not use userLogin here as well?

Not really, just thought using it for the key would be fine, but will do it for consistency's sake. Thank you for the suggestion.

…at-detail

npsedhain · 2021-04-13T12:30:36Z

@marcaaron, I have fixed the changes shown in the github actions folder and resolved conflicts.

NikkiWines · 2021-04-13T16:30:09Z

@npsedhain looks like there are still some conflicts here.

npsedhain · 2021-04-13T17:16:08Z

@NikkiWines Will fix them ASAP.

…at-detail

npsedhain · 2021-04-13T17:22:41Z

@NikkiWines Done!

src/libs/Navigation/AppNavigator/ModalStackNavigators.js

marcaaron · 2021-04-13T17:45:40Z

src/libs/Navigation/linkingConfig.js

+            Participants: {
+                screens: {
+                    Participants_Root: ROUTES.REPORT_PARTICIPANTS,
+                    Details_Root: ROUTES.REPORT_PARTICIPANT,


Ok now it is a blocker because I think we cannot have Details_Root existing in two navigators? Can we change this to:

ReportParticipants_Root
ReportParticipants_Details

marcaaron · 2021-04-13T18:03:29Z

src/pages/DetailsPage.js

@@ -37,12 +40,14 @@ const DetailsPage = ({personalDetails, route}) => {
        <ScreenWrapper>
            <HeaderWithCloseButton
                title="Details"
+                shouldShowBackButton={!!route.params.reportID}


This feels like an implementation detail. Can we make this more explicit by adding something above like:

// If we have a reportID param this means that we arrived here via the ParticipantsPage and should be allowed to navigate back to it const shouldShowBackButton = Boolean(route.params.reportID);

NikkiWines

Code looks good, but I'm seeing an issue where I can't see the details page for an account with an SMS login though their details do exist. Looks like it's because of login: userLogin, which should be using login in that case. My bad for not catching that when I recommended that change earlier.

Screen.Recording.2021-04-13.at.11.05.29.AM.mov

Screen.Recording.2021-04-13.at.11.06.38.AM.mov

npsedhain · 2021-04-14T09:16:21Z

@marcaaron @NikkiWines
Hey, guys, I've made the changes. Feel free to let me know how this looks.

marcaaron

Thanks for your patience and for all the changes. LGTM.

NikkiWines

Looks great 👍

marcaaron · 2021-04-14T17:47:16Z

All yours @Luke9389

Luke9389 · 2021-04-14T18:18:04Z

Thanks for helping with the reviews @marcaaron and @NikkiWines

OSBotify · 2021-04-14T18:19:01Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

laurenreidexpensify · 2021-04-15T09:50:51Z

Thanks @npsedhain - we will issue payment on 21 April assuming no regressions.

npsedhain · 2021-04-15T10:25:08Z

Thanks @laurenreidexpensify, but I think you tagged the wrong person. 😅

laurenreidexpensify · 2021-04-15T10:41:32Z

Sorry @npsedhain!!! My bad 🤦🏽‍♀️

OSBotify · 2021-04-19T22:41:56Z

🚀 [Deployed](https://github.com/Expensify/Expensify.cash
/actions/runs/765130740) 🚀 to
staging on Mon Apr 19 2021 at 22:41:56 GMT+0000 (Coordinated Universal Time)

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

npsedhain requested a review from a team as a code owner March 31, 2021 20:42

MelvinBot requested review from Luke9389 and removed request for a team March 31, 2021 20:43

Luke9389 suggested changes Apr 1, 2021

View reviewed changes

Luke9389 requested a review from NikkiWines April 1, 2021 00:45

NikkiWines requested changes Apr 1, 2021

View reviewed changes

marcaaron requested changes Apr 2, 2021

View reviewed changes

npsedhain changed the title ~~Create a group chat info view with participants information.~~ [WIP] Create a group chat info view with participants information. Apr 3, 2021

npsedhain changed the title ~~[WIP] Create a group chat info view with participants information.~~ Create a group chat info view with participants information. Apr 6, 2021

marcaaron assigned npsedhain Apr 6, 2021

marcaaron requested changes Apr 6, 2021

View reviewed changes

npsedhain added 5 commits April 8, 2021 09:25

Create a group chat info view with participants information.

303db86

Resolved PR comments and made code cleaner.

255e4ec

Refactor: Make suggested changes and refactor the participants page s…

2a5ddb3

…ubscriptions.

Make the details page not leave the participants navigator.

27e1175

Refactor: Make the suggested enchancements.

c0592bf

npsedhain force-pushed the npsedhain-groupchat-detail branch from 1a8df7c to c0592bf Compare April 8, 2021 04:22

Fix the github action check failing.

6789c86

marcaaron requested changes Apr 9, 2021

View reviewed changes

NikkiWines requested changes Apr 9, 2021

View reviewed changes

Refactor: Added conditional rendering for back button and other changes.

1a2560e

marcaaron requested changes Apr 12, 2021

View reviewed changes

NikkiWines reviewed Apr 12, 2021

View reviewed changes

npsedhain added 3 commits April 13, 2021 17:32

Merge remote-tracking branch 'upstream/master' into npsedhain-groupch…

d4cc1e0

…at-detail

Revert the changes made in the github action files.

2ae878a

Fix the github action issue.

958b7a8

Merge remote-tracking branch 'upstream/master' into npsedhain-groupch…

f0b4a4d

…at-detail

marcaaron requested changes Apr 13, 2021

View reviewed changes

NikkiWines requested changes Apr 13, 2021

View reviewed changes

Refactor: Changed the navigators as suggested.

7c9be34

marcaaron approved these changes Apr 14, 2021

View reviewed changes

NikkiWines approved these changes Apr 14, 2021

View reviewed changes

marcaaron requested a review from Luke9389 April 14, 2021 17:47

Luke9389 approved these changes Apr 14, 2021

View reviewed changes

Luke9389 merged commit 90f3ceb into Expensify:master Apr 14, 2021

		@@ -82,8 +82,6 @@ module.exports = run;

		const _ = __nccwpck_require__(4987);

Create a group chat info view with participants information. #2178

Create a group chat info view with participants information. #2178

Conversation

npsedhain commented Mar 31, 2021

Details

Fixed Issues

Tests

Tested On

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Luke9389 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Luke9389 Apr 1, 2021 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

npsedhain commented Apr 1, 2021

Luke9389 commented Apr 1, 2021

NikkiWines left a 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

trjExpensify commented Apr 2, 2021

marcaaron left a 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

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

npsedhain commented Apr 6, 2021

marcaaron commented Apr 6, 2021 • edited Loading

trjExpensify commented Apr 6, 2021

marcaaron left a 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

Choose a reason for hiding this comment

Choose a reason for hiding this comment

marcaaron commented Apr 6, 2021

Luke9389 commented Apr 6, 2021

marcaaron commented Apr 6, 2021

npsedhain commented Apr 7, 2021

npsedhain commented Apr 8, 2021

marcaaron left a 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

NikkiWines left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

npsedhain commented Apr 11, 2021

Choose a reason for hiding this comment

NikkiWines left a comment

Luke9389 Apr 1, 2021 •

edited

Loading

marcaaron commented Apr 6, 2021 •

edited

Loading

laurenreidexpensify commented Apr 15, 2021 •

edited

Loading