Fix frequently used emojis list doesn't get updated when adding emojis by typing emoji code with colon by bernhardoj · Pull Request #18396 · Expensify/App

bernhardoj · 2023-05-04T08:18:25Z

Details

We are not updating the frequently used emojis list when adding emojis by typing emoji code with colon in the composer. This PR will make sure the list is updated.

Fixed Issues

$ #17599
PROPOSAL: #17599 (comment)

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

No request will be called while offline

QA Steps

There are 2 ways to test this:
Simple way to test

Open a chat.
Type an emoji code that is not in your frequently used emoji list in the composer with colon, for example :wave:.
Open the emoji picker and verify that the typed emoji is added to the Frequently Used emoji list.
Edit the message.
Repeat step 2 in the edit composer.
Open the emoji picker and verify that the typed emoji is added to the frequently used emoji list.

A bit technical way to test

First of all, open the Network Tab.

Web (Safari)

Open Safari > Settings
Open Advanced Tab
Check Show Develop menu
Open Develop menu > Show JavaScript console
Switch to Network Tab

Desktop

Open View > Toggle Developer Tools
Switch to Network tab

mWeb (Safari)

Open Safari > Settings
Open Advanced Tab
Check Show Develop menu
Open Develop menu > [iOS Device Name, e.g. Simulator - iPhone 14 - iOS 16.2] > Choose New Expensify url
It will open a Web Inspector. Switch to Network Tab

mWeb (Chrome)

Open Chrome
Go to chrome://inspect
Look for the New Expensify url and click inspect
It will open an inspector. Switch to Network Tab

Native
I don't think there is a Network Tab in native, so to see the request is being made, we can look at the terminal (dev only)

Open any chat
Type :smile: in the composer
Verify UpdateFrequentlyUsedEmojis request is being made in the Network Tab
Send a message
Edit the message
Type :smile: in the edit composer
Verify UpdateFrequentlyUsedEmojis request is being made in the Network Tab

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Web

Screen.Recording.2023-05-04.at.15.12.04.mov

Mobile Web - Chrome

Screen.Recording.2023-05-04.at.15.27.42.mov

Mobile Web - Safari

Screen.Recording.2023-05-04.at.15.20.48.mov

Desktop

Screen.Recording.2023-05-04.at.15.16.13.mov

iOS

Screen.Recording.2023-05-04.at.15.25.08.mov

Android

Screen.Recording.2023-05-04.at.15.30.40.mov

… is added by emoji code and colon

MelvinBot · 2023-05-04T08:18:31Z

@MonilBhavsar @fedirjh One of you needs to 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]

bernhardoj · 2023-05-04T08:45:15Z

Here is additional video showing the count is added correctly.

Screen.Recording.2023-05-04.at.16.23.02.1.mov

fedirjh

Over all looks good, left a suggestion to refactor addToFrequentlyUsedEmojis

fedirjh · 2023-05-05T00:59:24Z

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-05-06.at.2.34.03.AM.mov

Mobile Web - Chrome

Screen.Recording.2023-05-08.at.5.45.52.PM.mov

Mobile Web - Safari

Screen.Recording.2023-05-08.at.4.46.53.PM.mov

Desktop

Screen.Recording.2023-05-06.at.2.30.40.AM.mov

iOS

Screen.Recording.2023-05-06.at.2.35.33.AM.mov

Android

Screen.Recording.2023-05-08.at.5.48.04.PM.mov

bernhardoj · 2023-05-05T05:57:02Z

@fedirjh Addressed the suggestion with a little bit differences and addition.

We can't use the suggestion name as the emoji name as the suggestion is different. I also pass the types so the emoji skin works for the frequent emoji list.

fedirjh · 2023-05-05T18:18:53Z

+    const frequentEmojiListOrdered = lodashOrderBy(mergedEmojisWithFrequent, ['count', 'lastUpdatedAt'], ['desc', 'desc'])
+        .slice(0, maxFrequentEmojiCount);


@bernhardoj Thanks for the update. While testing, I noticed that we missed the case where we select a new emoji from the emoji picker. The newly selected emoji should appear on the frequent list. However, the above changes do not account for that case. Therefore, we need to fix it. Here is a simple fix:

Suggested change

const frequentEmojiListOrdered = lodashOrderBy(mergedEmojisWithFrequent, ['count', 'lastUpdatedAt'], ['desc', 'desc'])

.slice(0, maxFrequentEmojiCount);

let frequentEmojiListOrdered = lodashOrderBy(mergedEmojisWithFrequent, ['count', 'lastUpdatedAt'], ['desc', 'desc']);

if (uniqueEmojisWithCounts.length === 1 && _.last(frequentEmojiListOrdered).name === uniqueEmojisWithCounts[0].name) {

frequentEmojiListOrdered.splice(maxFrequentEmojiCount, 1);

} else {

frequentEmojiListOrdered = frequentEmojiListOrdered.slice(0, maxFrequentEmojiCount);

}

It works fine for me though. Can you share your repro steps?

Screen.Recording.2023-05-06.at.09.00.57.mov

@bernhardoj Your emojis should have count > 1 , because we are ordering the emojis by count, if the newly added is the last in the list , it will be removed , check explanation

emoji.mov

I'm not aware the video I attached is a link. updated.

The emoji I add is a new emoji (the monkey emoji), not an emoji with count > 1

Ah, I think I understand.

My bad. That's what will happen with the new behavior. Updated my comment.

which means with the new behavior, no matter how many times we insert the new emoji, it won't be added to the list (because the count is always 0).

I'm not sure if we're on the same page. Which count are you referring to? The current behavior is to extract emojis from the copy/pasted comment, group them by emoji name, and assign each emoji a count that corresponds to the number of occurrences in the comment. Then, we merge this list with the old frequently used emojis list.

The count on the frequent emoji list. Let say all 24 emoji has count of 2. Then, we add a new emoji. Because it doesn't exist in the list, it will have a count of 1. With our new logic, we won't take the new emoji. The next time we add the same emoji, the count will still be 1 because it doesn't exist in the list.

@bernhardoj That’s why I suggested these changes here , If the last emoji in the list is the inserted emoji then We shouldn’t remove it , and we remove the previous emoji.

Updated to solve the issue. Also added a test.

fedirjh · 2023-05-05T18:48:37Z

@bernhardoj I think the testing steps could be simplified. We can check if the emoji is added to the frequently used list in the emoji picker. This is because the request is made when the frequently used list is updated. The steps could be:

Open a chat.
Type an emoji that is not in your frequently used emoji list in the composer.
Send the message.
Open the emoji picker and verify that the typed emoji is added to the frequently used emoji list.
Edit the message.
Type another emoji that is not in your frequently used emoji list in the edit composer.
Open the emoji picker and verify that the typed emoji is added to the frequently used emoji list.

bernhardoj · 2023-05-06T01:07:01Z

The new steps sounds good. I added it as an alternative for QA.

fedirjh

Left some comments

fedirjh · 2023-05-07T00:02:32Z

+                        ...frequentlyEmojisList.slice(0, (-1 - (newEmoji.length - 1))),
+                        ..._.map(newEmoji.slice(1), e => ({...e, count: 1, lastUpdatedAt: currentTime})),
+                    ];
+                    expect(spy).toBeCalledWith(expectedFrequentlyEmojisList);


we should expect that FrequentlyEmojisList length doesn’t exceed the max allowed value

expectedFrequentlyEmojisList.length === (CONST.EMOJI_FREQUENT_ROW_COUNT * CONST.EMOJI_NUM_PER_ROW)

expectedFrequentlyEmojisList is the array that we construct ourself. Testing the length is not needed.

Not totally agree here, the length should not pass the (CONST.EMOJI_FREQUENT_ROW_COUNT * CONST.EMOJI_NUM_PER_ROW) and we should test that

I think I got your point, but honestly I found it's weird to test an expected result. So, I add the length check to the frequentlyEmojisList length instead.

bernhardoj · 2023-05-07T09:52:09Z

@fedirjh Here is the explanation of why our current logic is wrong:

Let say a user already has 24 frequently used emojis with a count of 2.

First, let's agree on what should be the expected behavior when we insert multiple emojis at the same time. I expect it should have the same behavior of inserting single emoji multiple times (lmk if you disagree).

First case
Previously, we are talking about the issue that inserting a new emoji to a full list with count > 1 won't work. Then, I decided to use this fix f1184b8#diff-31af63e60e05edaca5584223a4cb595c02d2a3487e916c01b44846a5e9f8ec95R199 which could lead to negative value, but let's ignore that for now. Let say the number of emoji we want to insert is 5.
If we insert those at the same time, it means we will remove last 5 item from the list, then insert the 5 new emojis.

24 frequent emojis, remove last 5
19 frequent emojis, insert 5 new emojis
24 frequent emojis

However, if we insert them one by one (from emoji picker), then it will only replace the last emoji from the list.

24 frequent emojis, remove last 1
23 frequent emojis, insert 1 new emoji
24 frequent emojis, remove last 1
keep repeat...

You can notice that when inserting multiple emojis, we will replace 4 other different emojis.

Let say somehow we fix it so they have the same behavior, we still have the 2nd case.

Second case
With our current logic, inserting multiple emojis at the same time will group the same emoji and count them. This will have a different outcome for this case:

The user then insert multiple new emojis, A, B, and A again from emoji picker and emoji code with colon (:smile:). Here is what happen:

Insert one by one from emoji picker
First, insert A. Emoji A will be put at the last item of frequently used emojis list with count of 1.
Next, insert B. Emoji B will replace emoji A position with count of 1.
Last, insert A again. Emoji A will replace emoji B position with count of 1.

The final result is: 23 frequently used emojis + A emoji with a count of 1

Insert multiple emojis at the same time by emoji code
Let say the emoji code is :A: and :B:. So, the user paste into the composer this text :A: :B: :A:
The emojis are grouped which makes the emoji A has a count of 2 and B has a count of 1.

First, insert A. Emoji A will be put at the last item of frequently used emojis list with count of 2.
Next, insert B. Emoji B will replace emoji A position with count of 1.

The final result is: 23 frequently used emojis + B emoji with a count of 1

Conclusion
I think we should use the previous logic, of course with a modification to support emoji array. Here is how it looks: (almost the same with prev logic, just with a loop)

let frequentEmojiList = [...frequentlyUsedEmojis];

const maxFrequentEmojiCount = (CONST.EMOJI_FREQUENT_ROW_COUNT * CONST.EMOJI_NUM_PER_ROW) - 1;
const currentTimestamp = moment().unix();
_.each([].concat(newEmoji), (emoji) => {
    let currentEmojiCount = 1;
    const emojiIndex = _.findIndex(frequentEmojiList, e => e.code === emoji.code);
    if (emojiIndex >= 0) {
        currentEmojiCount = frequentEmojiList[emojiIndex].count + 1;
        frequentEmojiList.splice(emojiIndex, 1);
    }
    const updatedEmoji = {...emoji, ...{count: currentEmojiCount, lastUpdatedAt: currentTimestamp}};

    // We want to make sure the current emoji is added to the list
    // Hence, we take one less than the current frequent used emojis
    frequentEmojiList = frequentEmojiList.slice(0, maxFrequentEmojiCount);
    frequentEmojiList.push(updatedEmoji);

    // Sort the list after adding a new emoji to the frequent used emojis list
    frequentEmojiList = lodashOrderBy(frequentEmojiList, ['count', 'lastUpdatedAt'], ['desc', 'desc']);
});

User.updateFrequentlyUsedEmojis(frequentEmojiList);

Complexity
M = new emojis
N = frequent emojis

M * (N + N log N) which I think could be simplified to M * N log N.

This is assuming the sort is N log N.

Let me know if it make sense to you and I will commit it.

fedirjh · 2023-05-08T01:18:53Z

@bernhardoj Okay, thank you for the explanation, that make sense. I think we can proceed with that implementation 🟢

…-emoji-code

bernhardoj · 2023-05-08T03:53:51Z

Great. Updated.

Just a note: it is slow when pasting > 1000 emojis code

fedirjh · 2023-05-08T16:21:32Z

@bernhardoj Code looks good. units test are failing , please fix it .

bernhardoj · 2023-05-08T16:23:29Z

Hmm. I see all the test jobs are green. Maybe it becomes flaky (I'm guessing it reruns after your new comment) after changing it to native sort? I will try run the test multiple times locally.

fedirjh · 2023-05-08T16:33:02Z

cc @bernhardoj looks good , I just forgot to revert some changes I did for testing 😕

bernhardoj · 2023-05-08T16:34:13Z

Hmm, it's really weird, the test in CI and my device is working fine.

can you log the final frequentEmojiList array in addToFrequentlyUsedEmojis and tell which one of the test is failing (the name)?

bernhardoj · 2023-05-08T16:40:32Z

Ah okay, that's great to hear (or read). I was confused why you suddenly comment "looks good" only 🤣.

fedirjh

Looks good and tests well 🚀

cc @MonilBhavsar over to you

MonilBhavsar · 2023-05-10T17:18:44Z

Hi! Apologies for delay. Some priority issues took me aside. But I'll review it now.
@bernhardoj sorry there are some conflicts to fix 😬
Most probably should be prettier changes, as we merged it last night

MonilBhavsar

Looks good, couple of NAB's..

MonilBhavsar · 2023-05-10T18:30:41Z

+            // Given an existing frequently used emojis list with count > 1
+            const frequentlyEmojisList = [
+                {
+                    code: '👋', name: 'wave', count: 2, lastUpdatedAt: 4,


let's try to mimic real data as much as possible by using unix timestamp in lastUpdatedAt?

Personally, I think it's fine to have a simple number instead of unix timestamp as it's easier to read. The purpose of lastUpdatedAt is to show which emoji is used the most recent and I think as long as the number can represent that clearly, then it's fine.

MonilBhavsar · 2023-05-10T18:31:38Z

+                    code: '💯', name: '100', count: 2, lastUpdatedAt: 2,
+                },
+                {
+                    code: '👿', name: 'imp', count: 2, lastUpdatedAt: 1,


Lol, today I learnt, this emoji is named as imp 😄

MonilBhavsar · 2023-05-10T18:37:40Z

@bernhardoj @fedirjh
I appreciate the collaborative work, adding the automated tests and talking about performance 🚀 🙇

…-emoji-code

bernhardoj · 2023-05-11T05:03:04Z

Merged with main.

OSBotify · 2023-05-12T07:28:09Z

✋ 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-05-15T09:19:56Z

🚀 Deployed to staging by https://github.com/MonilBhavsar in version: 1.3.14-0 🚀

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

OSBotify · 2023-05-17T00:19:46Z

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.3.14-14 🚀

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

bernhardoj added 2 commits May 4, 2023 15:49

remove frequent emoji list onyx connection

9448c83

connect with frequent emojis list onyx and update the list when emoji…

4f94c44

… is added by emoji code and colon

bernhardoj requested a review from a team as a code owner May 4, 2023 08:18

melvin-bot Bot requested review from MonilBhavsar and fedirjh and removed request for a team May 4, 2023 08:18

fedirjh reviewed May 5, 2023

View reviewed changes

Comment thread src/libs/EmojiUtils.js Outdated

Comment thread src/libs/EmojiUtils.js

Comment thread src/libs/EmojiUtils.js Outdated

Comment thread src/libs/EmojiUtils.js

improve the logic

b0eeb72

fedirjh reviewed May 5, 2023

View reviewed changes

bernhardoj added 4 commits May 6, 2023 18:03

fix can't add new emoji to the list

f1184b8

add test

a9e689e

fix typo

9b780a5

add comment

3490d46

fedirjh reviewed May 7, 2023

View reviewed changes

bernhardoj added 2 commits May 8, 2023 11:39

Merge branch 'main' into fix/17599-no-frequent-emoji-update-by-typing…

1efc145

…-emoji-code

use the old logic back but with looping

a414ef0

fedirjh reviewed May 8, 2023

View reviewed changes

Comment thread src/libs/EmojiUtils.js Outdated

using js native sort as lodash is much slower

c277e87

This comment was marked as outdated.

Sign in to view

fedirjh previously approved these changes May 8, 2023

View reviewed changes

MonilBhavsar reviewed May 10, 2023

View reviewed changes

bernhardoj added 2 commits May 11, 2023 12:47

Merge branch 'main' into fix/17599-no-frequent-emoji-update-by-typing…

9521a0f

…-emoji-code

prettier

4c8af67

bernhardoj dismissed fedirjh’s stale review via 4c8af67 May 11, 2023 04:58

MonilBhavsar approved these changes May 12, 2023

View reviewed changes

MonilBhavsar merged commit 615ebd9 into Expensify:main May 12, 2023

OSBotify mentioned this pull request May 15, 2023

Deploy Checklist: New Expensify 2023-05-15 #18938

Closed

67 tasks

melvin-bot Bot mentioned this pull request May 16, 2023

[HOLD for payment 2023-05-23] [$1000] No api call to UpdateFrequentlyUsedEmojis when entered via colon commands #17599

Closed

6 tasks

		const frequentEmojiListOrdered = lodashOrderBy(mergedEmojisWithFrequent, ['count', 'lastUpdatedAt'], ['desc', 'desc'])
		.slice(0, maxFrequentEmojiCount);

-    const frequentEmojiListOrdered = lodashOrderBy(mergedEmojisWithFrequent, ['count', 'lastUpdatedAt'], ['desc', 'desc'])
-        .slice(0, maxFrequentEmojiCount);
+        let frequentEmojiListOrdered = lodashOrderBy(mergedEmojisWithFrequent, ['count', 'lastUpdatedAt'], ['desc', 'desc']);
+    if (uniqueEmojisWithCounts.length === 1 && _.last(frequentEmojiListOrdered).name === uniqueEmojisWithCounts[0].name) {
+        frequentEmojiListOrdered.splice(maxFrequentEmojiCount, 1);
+    } else {
+        frequentEmojiListOrdered = frequentEmojiListOrdered.slice(0, maxFrequentEmojiCount);
+    }

Uh oh!

Conversation

bernhardoj commented May 4, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

MelvinBot commented May 4, 2023

Uh oh!

bernhardoj commented May 4, 2023

Uh oh!

fedirjh left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

fedirjh commented May 5, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

bernhardoj commented May 5, 2023

Uh oh!

Choose a reason for hiding this comment

Uh oh!

bernhardoj May 6, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

fedirjh May 6, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

fedirjh commented May 5, 2023

Uh oh!

bernhardoj commented May 6, 2023

Uh oh!

fedirjh left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

bernhardoj commented May 7, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

fedirjh commented May 8, 2023

Uh oh!

bernhardoj commented May 8, 2023

Uh oh!

Uh oh!

bernhardoj commented May 4, 2023 •

edited

Loading

fedirjh commented May 5, 2023 •

edited

Loading

bernhardoj May 6, 2023 •

edited

Loading

fedirjh May 6, 2023 •

edited

Loading

bernhardoj commented May 7, 2023 •

edited

Loading

bernhardoj commented May 8, 2023 •

edited

Loading

fedirjh commented May 8, 2023 •

edited

Loading