Migrate MoneyRequestParticipantsSplitSelector.js to function component #20271

multijump · 2023-06-06T14:36:11Z

Details

Migrate MoneyRequestParticipantsSplitSelector.js to function component

Fixed Issues

$ #16280
PROPOSAL: (#16280 (comment))

Tests

Click on FAB
Click on Split Money
Input money (ex: 15)
Click on Next button
Search Email or Name
Choose more than 1 user
Choose 8 users as maximum.
Click on Split $15 button
Showed split request in chat

Verify that no errors appear in the JS console

Offline tests

Follow the same steps listed in the section above

QA Steps

Follow the same steps listed in the section above

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 / Chrome
- iOS / native
- iOS / 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I 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 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(themeColors.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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Web.mov

Mobile Web - Chrome

Mobile.Web.-.Chrome.mov

Mobile Web - Safari

Mobile.Web.-.Safari.mov

Desktop

Desktop.mov

iOS

iOS.mov

Android

Android.mov

github-actions · 2023-06-06T14:36:28Z

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

melvin-bot · 2023-06-06T14:36:44Z

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

multijump · 2023-06-06T21:13:25Z

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

rushatgabhane · 2023-06-09T14:11:06Z

src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js

+            personalDetails,
+            userToInvite
+        });
+    }, [props.betas, props.reports, props.participants, props.personalDetails, searchTerm])


Hi @multijump, I think we should re-render if props.translate changes also.

i.e. if the language is changed on device B, device A should re-render.
Does that make sense?

Hi, @rushatgabhane
Yes, that make sense.
just updated following your instruction.
Thanks.

rushatgabhane

@multijump keyboard navigation isn't working on split bill page

multijump · 2023-06-09T15:16:43Z

@multijump keyboard navigation isn't working on split bill page

Hi, @rushatgabhane
As you can see, It seems keyboard navigation is not related with this issue.

return (
      <View style={[styles.flex1, styles.w100, props.participants.length > 0 ? props.safeAreaPaddingBottomStyle : {}]}>
          <OptionsSelector
              canSelectMultipleOptions
              sections={sections}
              selectedOptions={props.participants}
              value={searchTerm}
              onSelectRow={toggleOption}
              onChangeText={setSearchTerm}
              headerMessage={headerMessage}
              boldStyle
              shouldShowConfirmButton
              confirmButtonText={props.translate('common.next')}
              onConfirmSelection={finalizeParticipants}
              textInputLabel={props.translate('optionsSelector.nameEmailOrPhoneNumber')}
              safeAreaPaddingBottomStyle={props.safeAreaPaddingBottomStyle}
              shouldShowOptions={isOptionsDataReady}
          />
      </View>
  );

I think it is related with OptionsSelector component.
Should I change the OptionsSelector component too?

rushatgabhane · 2023-06-09T15:30:29Z

@multijump it's failing on this PR only, right?

If It's working on main then we need to fix it

multijump · 2023-06-09T15:50:20Z

@rushatgabhane
Actually, keyboard navigation in this branch is working the same as https://new.expensify.com/split/new
I am not sure what was the keyboard navigation you mean.
can you please let me know failed case?

rushatgabhane · 2023-06-11T22:00:14Z

@multijump @Julesssss sorry im out sick and won't be able to review this PR in time.

@allroundexperts on c+ channel said that they're taking over, thanks!

Julesssss · 2023-06-12T07:42:43Z

Hey @allroundexperts, just wanted to double check your taking over the review? If so I'll update the linked issue.

allroundexperts · 2023-06-12T08:38:56Z

Hey @allroundexperts, just wanted to double check your taking over the review? If so I'll update the linked issue.

Yes. I'll be reviewing this today.

…to 16280_refactor_MoneyRequestParticipantsSplitSelector

allroundexperts · 2023-06-16T12:00:19Z

src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js

+            personalDetails,
+            userToInvite,
+        });
+        props.onAddParticipants(newSelectedOptions);


Why are you changing the order here?

Hi, @allroundexperts
There was not special reason.
I thought simply props change (for participants) doesn't affect to toggleOption function running so it doesn't matter where it is.
But I thought changing order was more readable and understandable.
If you require to change the order, I will change it.

It's very difficult to compare the before and after code with the order changed. Can you please change the order as it was previously? Thanks!

Hi, @allroundexperts
Restored order per your request.

allroundexperts · 2023-06-16T12:01:22Z

src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js

+        setNewChatOptions({
+            recentReports,
+            personalDetails,
+            userToInvite,
+        });


Please use this inside the callback like it was being done previously.

@allroundexperts
This setState doesn't depend on previous state so previousState will be the unused variable.
Do we need to implement to use the callback?

allroundexperts · 2023-06-16T12:02:22Z

src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js

+     * Once a single or more users are selected, navigates to next step
+     */
+    const finalizeParticipants = () => {
+        props.onStepComplete();
+    };


Again, why is the order being changed here?

Hi, @allroundexperts
There is no reason.
I paid more attention to convert toggleOption and getSections function because these functions are main functions in this component.
So I converted them first and then finalizeParticipants.
That's why changed the order.

Just for my understanding, why don't we use withCallback here? I assume it's not necessary, but I'm still trying to understand hooks.

I think we don't need to even wrap this inside the function since the function does nothing other than calling the function supplied in the prop. @multijump can you please remove this and use the prop directly?

Hi, @allroundexperts
Updated to use the prop directly.

allroundexperts · 2023-06-21T23:46:36Z

src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js

-        this.props.onStepComplete();
-    }
+        return newSections;
+        // eslint-disable-next-line react-hooks/exhaustive-deps -- props does not need to be a dependency as it will always exist


Why are you disabling this check?

I got this warning when I checked lint. So I checked the useMemo and useCallback functions in other components and I noticed they did same comment. That's why I disabled it.

It seems like we're no longer disabling the check, but I think it dows make sense, right? We shouldn't update after ANY prop is changed, just specific ones?

That's correct @Julesssss. We've added into dependency all the properties that should trigger a re-calculation of values in the function.

allroundexperts · 2023-06-21T23:46:55Z

src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js

+                setSearchTerm('');
+            }
+        },
+        // eslint-disable-next-line react-hooks/exhaustive-deps -- props does not need to be a dependency as it will always exist


Same question

I got a warning when I checked lint. So I checked the useMemo and useCallback functions in other components and I noticed they did same comment. That's why I disabled it.

allroundexperts · 2023-06-21T23:47:42Z

@multijump It's looking good largely. Can you please resolve the conflict and reply to a few more comments?

…Selector

multijump · 2023-06-23T20:42:42Z

@multijump It's looking good largely. Can you please resolve the conflict and reply to a few more comments?

Hi, @allroundexperts
I fixed conflicts and replied to your comments.
Thanks

allroundexperts · 2023-06-23T20:43:40Z

@multijump It's looking good largely. Can you please resolve the conflict and reply to a few more comments?

Hi, @allroundexperts I fixed conflicts and replied to your comments. Thanks

Thanks @multijump!
I am on it now.

allroundexperts · 2023-06-23T22:37:01Z

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 / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.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 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

Web

Screen.Recording.2023-06-24.at.3.08.33.AM.mov

Mobile Web - Chrome

Screen.Recording.2023-06-24.at.3.25.06.AM.mov

Mobile Web - Safari

Screen.Recording.2023-06-24.at.3.24.23.AM.mov

Desktop

Screen.Recording.2023-06-24.at.3.12.27.AM.mov

iOS

Screen.Recording.2023-06-24.at.3.26.18.AM.mov

Android

Screen.Recording.2023-06-24.at.3.29.56.AM.mov

allroundexperts

Looking good. Thanks for the changes and your patience @multijump!

allroundexperts · 2023-06-24T00:37:53Z

Actually, we had another discussion here and it was decided that we'll be favouring prop de-structuring instead disabling the exhastive-dependency lint rule. @multijump Can you please make the changes? Should be fairly quick.

…to 16280_refactor_MoneyRequestParticipantsSplitSelector

…Selector

multijump · 2023-06-25T19:28:50Z

Actually, we had another discussion here and it was decided that we'll be favouring prop de-structuring instead disabling the exhastive-dependency lint rule. @multijump Can you please make the changes? Should be fairly quick.

Hi, @allroundexperts
Destructured props and removed lint disable.

Julesssss · 2023-07-03T07:48:07Z

@allroundexperts could you please resolve the threads that have been addressed, thanks.

allroundexperts · 2023-07-04T07:32:10Z

@allroundexperts could you please resolve the threads that have been addressed, thanks.

@Julesssss All threads have been fixed. I can not resolve them because I just commented on the lines.

Julesssss · 2023-07-04T08:45:52Z

Tests well

OSBotify · 2023-07-04T08:50:13Z

✋ 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 · 2023-07-05T17:31:44Z

🚀 Deployed to staging by https://github.com/Julesssss in version: 1.3.37-0 🚀

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

allroundexperts · 2023-07-06T07:22:41Z

@Julesssss This took a lot of time to review back and forth. If possible, can we please consider bumping this to our standard bounty price of $1k?

Julesssss · 2023-07-06T11:04:05Z

I agree this took longer than average, but personally, I think that balances out against simpler reviews that still have the $1000 bounty. Also, I don't think the bounty itself should be updated, as it would encourage that a slower contributor PR ends up being paid more than a faster one.

If you disagree I'm happy to share with others internally though to get more peoples thoughts! Let me know what you think.

allroundexperts · 2023-07-06T11:07:57Z

I agree this took longer than average, but personally, I think that balances out against simpler reviews that still have the $1000 bounty. Also, I don't think the bounty itself should be updated, as it would encourage that a slower contributor PR ends up being paid more than a faster one.

If you disagree I'm happy to share with others internally though to get more peoples thoughts! Let me know what you think.

Nopes. I agree with you 👍

Julesssss · 2023-07-06T12:27:15Z

Great, thanks for understanding. Maybe the circumstances will be different next time 👍

OSBotify · 2023-07-07T10:37:10Z

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.37-7 🚀

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

Migrate MoneyRequestParticipantsSplitSelector.js to function component

f8661e7

multijump requested a review from a team as a code owner June 6, 2023 14:36

melvin-bot bot requested review from marcaaron and removed request for a team June 6, 2023 14:36

multijump mentioned this pull request Jun 6, 2023

[HOLD for payment 2023-07-14] [$250] Migrate MoneyRequestParticipantsSplitSelector.js to function component #16280

Closed

1 task

Julesssss assigned multijump Jun 6, 2023

Julesssss requested review from Julesssss and rushatgabhane June 6, 2023 14:46

multijump added 2 commits June 7, 2023 00:01

Fixed lint issues

8ecd4fb

Revert podfile.lock

0b66de4

Fix

e10cd88

rushatgabhane reviewed Jun 9, 2023

View reviewed changes

rushatgabhane suggested changes Jun 9, 2023

View reviewed changes

added translate per reviewer request

35b3f79

Julesssss requested a review from allroundexperts June 12, 2023 07:41

multijump added 3 commits June 12, 2023 17:57

fixed lint issues

4c375f9

fixed conflicts from main branch

041d782

Merge branch 'main' of gh.neting.cc-avastorm:multijump/Expensify-App in…

c068bfb

…to 16280_refactor_MoneyRequestParticipantsSplitSelector

allroundexperts reviewed Jun 16, 2023

View reviewed changes

fixed lint issue

a1e5ba1

allroundexperts reviewed Jun 21, 2023

View reviewed changes

Merge branch 'main' into 16280_refactor_MoneyRequestParticipantsSplit…

05a9937

…Selector

allroundexperts approved these changes Jun 23, 2023

View reviewed changes

melvin-bot bot requested a review from Julesssss June 23, 2023 22:41

multijump added 2 commits June 25, 2023 21:53

Merge branch 'main' of gh.neting.cc-avastorm:multijump/Expensify-App in…

0afb3e6

…to 16280_refactor_MoneyRequestParticipantsSplitSelector

Merge branch 'main' into 16280_refactor_MoneyRequestParticipantsSplit…

b70b37e

…Selector

allroundexperts approved these changes Jul 2, 2023

View reviewed changes

Julesssss approved these changes Jul 4, 2023

View reviewed changes

Expensify deleted a comment from rushatgabhane Jul 4, 2023

Julesssss merged commit e23cd16 into Expensify:main Jul 4, 2023

OSBotify mentioned this pull request Jul 5, 2023

Deploy Checklist: New Expensify 2023-07-05 #22282

Closed

58 tasks

marcaaron mentioned this pull request Jul 5, 2023

Selecting user doesn't clear input text from search field on Split Bill page #22298

Closed

6 tasks

Migrate MoneyRequestParticipantsSplitSelector.js to function component #20271

Migrate MoneyRequestParticipantsSplitSelector.js to function component #20271

Conversation

multijump commented Jun 6, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

github-actions bot commented Jun 6, 2023 • edited Loading

melvin-bot bot commented Jun 6, 2023

multijump commented Jun 6, 2023

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rushatgabhane left a comment

Choose a reason for hiding this comment

multijump commented Jun 9, 2023 • edited Loading

rushatgabhane commented Jun 9, 2023

multijump commented Jun 9, 2023

rushatgabhane commented Jun 11, 2023

Julesssss commented Jun 12, 2023 • edited Loading

allroundexperts commented Jun 12, 2023

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

multijump Jun 20, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

allroundexperts commented Jun 21, 2023

multijump commented Jun 23, 2023

allroundexperts commented Jun 23, 2023

allroundexperts commented Jun 23, 2023

Reviewer Checklist

Screenshots/Videos

allroundexperts left a comment

Choose a reason for hiding this comment

allroundexperts commented Jun 24, 2023

multijump commented Jun 25, 2023

Julesssss commented Jul 3, 2023

allroundexperts commented Jul 4, 2023

Julesssss commented Jul 4, 2023

OSBotify commented Jul 4, 2023

OSBotify commented Jul 5, 2023

allroundexperts commented Jul 6, 2023

Julesssss commented Jul 6, 2023

allroundexperts commented Jul 6, 2023

Julesssss commented Jul 6, 2023

OSBotify commented Jul 7, 2023

multijump commented Jun 6, 2023 •

edited

Loading

github-actions bot commented Jun 6, 2023 •

edited

Loading

multijump commented Jun 9, 2023 •

edited

Loading

Julesssss commented Jun 12, 2023 •

edited

Loading

multijump Jun 20, 2023 •

edited

Loading