[CS2113-W13-3] EventManagerCLI #7

KuanHsienn · 2024-09-18T17:23:42Z

EventManagerCLI allows tutors/event managers to organize events and classes and keep track of participants progress. It is optimized for CLI users so that frequent tasks can be done more efficiently.

Mahesh1772

Great job overall! The code is solid, and the functionality is well-implemented. I only had a few minor recommendations, mainly around 'code readability' and 'SRP' , but nothing that detracts from the quality of the work. Thanks for the effort and attention to detail here!

Mahesh1772 · 2024-10-27T00:27:31Z

src/main/java/seedu/manager/event/Event.java

+    private Optional<Participant> getParticipantByName(String participantName) {
+        for (Participant participant : this.participantList) {
+            if (participant.getName().equalsIgnoreCase(participantName)) {
+                return Optional.of(participant);
+            }
+        }
+
+        return Optional.empty();
+    }


Consider moving the Private methods together at the end of the class and group them together and not have them in between Public methods

Mahesh1772 · 2024-10-27T00:30:23Z

src/main/java/seedu/manager/event/Event.java

+    /**
+     * Removes a participant from the participant list.
+     *
+     * <p>
+     * This method attempts to remove the specified participant from the list of
+     * participants associated with the event. It returns {@code true} if the
+     * participant was successfully removed, and {@code false} if the participant
+     * was not found in the list.
+     * </p>
+     *
+     * @param participantName the name of the participant to be removed from the list.
+     * @return {@code true} if the participant was successfully removed;
+     *         {@code false} if the participant was not found in the list.
+     */
+    public boolean removeParticipant(String participantName) {
+        return this.participantList.removeIf((participant) ->
+                (participant.getName().equalsIgnoreCase(participantName)));
+    }


Consider simplifying the documentation to be more concise while maintaining clarity. As of now Javadoc is longer than the actual method implementation. Since the method name is self explanatory and the @param and @return on the Javadoc explain the things clearly, make the description very concise, and not as long as the method

Mahesh1772 · 2024-10-27T00:34:42Z

src/main/java/seedu/manager/event/Event.java

+    /**
+     * Returns true if the participant with the given name can be marked present or absent.
+     * Returns false otherwise.
+     *
+     * @param participantName the name of the participant.
+     * @param isPresent true if the participant is to be marked present, false if he is to be marked absent.
+     * @return {@code true} if the participant with participantName has been marked present or absent,
+     *     {@code false} otherwise.
+     */
+    public boolean markParticipant(String participantName, boolean isPresent) {
+        Optional<Participant> participant = getParticipantByName(participantName);
+
+        if (participant.isEmpty()) {
+            return false;
+        }
+
+        participant.get().setPresent(isPresent);
+        return true;
+    }


Consider using SLAP, and limit one method to only one function. As of now, function contains code for : both participant lookup and status modification

Consider splitting into two methods for better single responsibility.

Mahesh1772 · 2024-10-27T00:35:59Z

src/main/java/seedu/manager/event/Event.java

+    public ArrayList<Participant> getParticipantList() {
+        return participantList;
+    }


Consider adding Javadocs to standardize how the document handles getter code.

Mahesh1772 · 2024-10-27T00:44:13Z

src/main/java/seedu/manager/parser/Parser.java

+    //@@author glenn-chew
+    /**
+     * Parses the input string to create a {@link Command} based on the provided command parts.
+     *
+     * <p>
+     * This method checks the command flag extracted from the command parts. If the command
+     * flag is {@code "-e"}, it splits the input string to create a {@link ViewCommand}
+     * for viewing the participants in the event.
+     * Otherwise, it throws an {@link InvalidCommandException} with an error message.
+     * </p>
+     *
+     * @param input        the input string containing the command details.
+     * @param commandParts an array of strings representing the parsed command parts,
+     *                     where the second element is the command flag.
+     * @return a {@link Command} object representing the parsed command.
+     * @throws InvalidCommandException if the flag is not matched.
+     */
+    private Command parseViewCommand(String input, String[] commandParts) throws InvalidCommandException {
+        assert commandParts[0].equalsIgnoreCase(ViewCommand.COMMAND_WORD);
+        try {
+            String commandFlag = commandParts[1];
+
+            if (commandFlag.equals("-e")) {
+                String [] inputParts = input.split("-e");
+                return new ViewCommand(inputParts[1].trim());
+            }
+
+            logger.log(WARNING,"Invalid command format");
+            throw new InvalidCommandException(INVALID_VIEW_MESSAGE);
+        } catch (IndexOutOfBoundsException exception) {
+            logger.log(WARNING,"Invalid command format");
+            throw new InvalidCommandException(INVALID_VIEW_MESSAGE);
+        }
+    }


Consider reducing the Javadocs description. The @params and @return make the code's functionality understandable and does not require a huge description. Rephrase the description to make it clearer and try to not make it as long as the method itself.

Mahesh1772 · 2024-10-27T00:50:06Z

src/main/java/seedu/manager/parser/Parser.java

+        } catch (IndexOutOfBoundsException exception) {
+            logger.log(WARNING,"Invalid command format");
+            throw new InvalidCommandException(INVALID_REMOVE_MESSAGE);
+        }


There's duplicate error handling code across parse methods. Consider extracting the common error handling pattern and making that a method

Mahesh1772 · 2024-10-27T00:52:40Z

src/main/java/seedu/manager/parser/Parser.java

+                String[] inputParts = input.split("-e|-s");
+                return getMarkEventCommand(inputParts[1].trim(), inputParts[2].trim());
+            } else if (commandFlag.equalsIgnoreCase("-p")) {
+                String[] inputParts = input.split("-p|-e|-s");


Consider extracting command flags into constants. That is, storing -p, -e, -s as constants.

Mahesh1772 · 2024-10-27T00:56:06Z

src/main/java/seedu/manager/storage/Storage.java

+    public void saveEvents(EventList events) throws IOException {
+        try (FileWriter writer = new FileWriter(filePath)) {
+            for (Event event : events.getList()) {
+                writer.write(event.getEventName() + "," + event.getEventTime() + ","
+                        + event.getEventVenue() + "\n"); // Save event details in CSV format
+            }
+        } catch (IOException exception) {
+            throw new IOException("Error saving events to file: " + filePath);
+        }
+    }


Consider saving Events with a different De-limiter and not comma ','. As if any name or event happens to have a dummy comma inside, it could break the code.

Mahesh1772 · 2024-10-27T00:58:16Z

src/main/java/seedu/manager/storage/Storage.java

+                }
+            }
+        } catch (IOException exception) {
+            throw new IOException("Error loading events from file: " + filePath + ".");


Consider adding what the exception which has occurred is

Mahesh1772 · 2024-10-27T01:03:55Z

src/main/java/seedu/manager/event/Event.java

+    public void addParticipant(String participantName) {
+        Participant participant = new Participant(participantName);
+        this.participantList.add(participant);


Consider adding code to verify if the participant is already in the list

TVageesan · 2024-10-30T02:31:15Z

docs/DeveloperGuide.md

+2. The user enters the command `mark -e Event 1 -s done` to mark `Event 1` as done. `MarkEventCommand` calls `MarkEventCommand#execute`,
+in which it gets the event `Event 1` from the event list, and sets its mark status to `true` or done.


Perhaps it would be helpful to use a state or class diagram to illustrate the program state here?

TVageesan · 2024-10-30T02:34:01Z

docs/DeveloperGuide.md

+2. Command Recognition:
+The `COMMAND_WORD` is set to "list", enabling the system to recognize the command input and invoke `ListCommand`.
+
+3. Execution of ListCommand#execute():


Should method calls be formatted as a code block (i.e. enclose with ``) as well?

TVageesan · 2024-10-30T02:36:22Z

docs/DeveloperGuide.md

+It uses the `String.format` method with `LIST_MESSAGE` to include the total number of events in the message header.
+Events are appended to `outputMessage` with numbered formatting for readability.


Can this be generalized as pseudocode? I.e. Does the developer need to know exactly how the message is created to understand how the feature wroks?

TVageesan · 2024-10-30T02:42:20Z

docs/DeveloperGuide.md

+
+Given below is an example usage scenario for the `add` mechanism, and how it behaves at each step.
+
+1. The user enters the command `add` followed by `-e` or `-p` to indicate adding an event or participant.


Does the developer need to know exactly what flags are being used to execute this command? Can it be generalized/explained in pseudo terms?

DarkDragoon2002

Overall Great Job but certain things are misrepresented in the code. Just needs minor changes. Great Job overall.

DarkDragoon2002 · 2024-10-30T04:22:37Z

docs/DeveloperGuide.md


 ## Non-Functional Requirements

-{Give non-functional requirements}
+* Should work for any **mainstream OS** as long as Java 17 is installed.

 ## Glossary


Please fill out the Glossary Items and Include the functions required for manual testing.

DarkDragoon2002 · 2024-10-30T04:38:51Z

docs/images/ArchitectureSequenceDiagram.png

Event should have a constructor and multiple Objects such as UI, Parser and Event need to be shown as objects. eg. ui:UI
Similar issues with most of the other diagrams. Otherwise very clear and helps with understanding!

DarkDragoon2002 · 2024-10-30T04:41:12Z

docs/DeveloperGuide.md

+| v2.0    | user     | mark events as completed                                        | easily track all past events                                                              |
+| v2.0    | user     | mark participants present                                       | know exactly who signed up but did not attend the event                                   |
+| v2.0    | user     | save events info                                                | can still access the information if the program terminates                                |
+| v2.0    | user     | filter events by keywords                                       | can find relevant information efficiently                                                 |


Filter and Find Commands seem to be implemented yet not mentioned here. It would be best to at least make a small mention of it above with a general description of how it works

DarkDragoon2002 · 2024-10-30T04:54:52Z

docs/DeveloperGuide.md

+2. The user enters the command `mark -e Event 1 -s done` to mark `Event 1` as done. `MarkEventCommand` calls `MarkEventCommand#execute`,
+in which it gets the event `Event 1` from the event list, and sets its mark status to `true` or done.
+
+3. The user then enters the command `mark -e Event 1 -s undone` to mark `Event 1` as not done. The `MarkEventCommand` again calls `MarkEventCommand#execute`,


Flag format is inconsistent. All of the Sequence Diagrams have the flags as e/ or p/ instead of -e or -p as stated in the text right above them. All of the above ones could use examples of the full format of the command like it is done for mark/unmark section

averageandyyy

Overall, more work needs to be done to better align the diagram to textbook expectations. Other more pressing concerns include description of the Participant class and consistency of usage flags/options. Do also consider the relevance and positon of the Storage class if it is being used by the various commands.

averageandyyy · 2024-10-31T01:05:25Z

docs/DeveloperGuide.md

+<img src = "images/ArchitectureSequenceDiagram.png">
+
+The above **Sequence Diagram** shows how the different components of the system interact with one
+another in the scenario when the command `add -e event -t 1200 -v venue` is executed.


For your sequence diagram here, to better align yourselves with the notation suggested in the textbook, might it be better to add colons to indicate that these are actual instances? For example, :Parser. From the textbook as well, I noticed that there was no need to specify the return type of the object that is being returned from a method.

Might you consider adding a User participant that interacts with Ui instead of Main?

Perhaps you can add colons to indicate that these are actual instances/objects instead of classes. This comment applies to all other sequence diagrams throughout the DG too.

averageandyyy · 2024-10-31T01:08:43Z

docs/DeveloperGuide.md

+
+### Storage component
+
+<img src = "images/StorageClassDiagram.png">


Might you consider adding the solid black triangles to indicate the directionality of the labels? While I am able to gather intuitively the directionality of most of the labels, I am unsure about that of the adopts label.

averageandyyy · 2024-10-31T01:09:57Z

docs/DeveloperGuide.md

+
+The `Command` component and its component classes are shown in the below **Class Diagram**:
+
+<img src = "images/CommandClassDiagram.png">


In describing the abstract Command class, might it be relevant to include at least the abstract method that all children Command classes are expected to implement?

averageandyyy · 2024-10-31T01:12:22Z

docs/DeveloperGuide.md

+The interactions between `Command` and other commands in the system is shown in the following _Sequence Diagram_:
+
+<img src = "images/CommandSequenceDiagram.png">


The diagram only describes the interaction between a single XYZCommand and the other components of the system, yet the text description above does not match the diagram as it says that it is showing interactions between various commands. Consider proofreading content before updating?

Thanks for catching this, was an oversight on our part (it was meant to be "components" rather than "commands")

averageandyyy · 2024-10-31T01:14:09Z

docs/DeveloperGuide.md

+
+The `Event` component and its component classes are shown in the below **Class Diagram**:
+
+<img src = "images/EventClassDiagram.png">


The introduction of Participant seems to be rather abrupt. Is Participant an actual class/object or is it referring to the user? The relationship here isn't obvious and well-documented and you might consider adding more content to clarify this?

Participant here is an actual class/object. Thanks for clarifying this, we'll add more details on the implementation of the Event component.

Also, we initially believed that it was clear from the class diagram that the Event class was composed of multiple Participant objects (with the multiplicity and association labels), and it would have been too much detail to describe it further.

averageandyyy · 2024-10-31T01:24:51Z

docs/DeveloperGuide.md

+**Add Participant**
+
+<img src = "images/AddParticipantSequenceDiagram.png">


See above comments regarding the AddEvent sequence diagram.

averageandyyy · 2024-10-31T01:27:22Z

docs/DeveloperGuide.md

+Given below is an example usage scenario for the `remove` mechanism, and how it behaves at each step.
+
+1. The user enters the command `remove` followed by `-e` or `-p` to specify removing an event or participant.
+2. This step is determined by our `Parser` which parses through the user input to determine if it is adding a participant or event
+3. Based on the parsed input, `RemoveComamnd` executes one of the following actions:
+   + **Remove Event:** Remove the specified event from `EventList` using the provided event name
+   + **Remove Participant:** Locates the event in `EventList` and deletes the specified participant
+4. If the event or participant is not found, `RemoveCommand` sets a failure message.
+
+The interactions between components during the execution of the `remove` command are show in the **Sequence Diagram** below:
+
+**Remove Event**
+
+<img src = "images/RemoveEventSequenceDiagram.png">


Conflict between the flags employed in the text description and diagram themselves. See above comment regarding the AddEvent sequence diagram.

averageandyyy · 2024-10-31T01:32:22Z

docs/DeveloperGuide.md

+
+**Remove Participant**
+
+<img src = "images/RemoveParticipantSequenceDiagram.png">


See above comment for AddEvent sequence diagram.

averageandyyy · 2024-10-31T01:34:09Z

docs/DeveloperGuide.md

+
+The interactions between components during the execution of the `view` command are show in the **Sequence Diagram** below:
+
+<img src = "images/ViewEventSequenceDiagram.png">


Similar to previous comments regarding Participant, if you have another relevant class like ParticipantList, it might be worth noting down its details in the DG?

Regarding Participant, see the above comment on the Event component.

averageandyyy · 2024-10-31T01:36:37Z

docs/DeveloperGuide.md

+
+The interactions between components during the execution of the `mark` command are show in the **Sequence Diagram** below:
+
+<img src = "images/MarkEventSequenceDiagram.png">


Great work! The sequence diagram here appears to be aligned with textbook requirements

yentheng0110

Overall LGTM, some changes are required to follow textbook conventions and coding standards

yentheng0110 · 2024-10-31T06:10:44Z

docs/DeveloperGuide.md

+
+### Interactions between components
+
+<img src = "images/ArchitectureSequenceDiagram.png">


Based on the textbook, the object deletion notation for Parser object to indicate the point at which it becomes ready to be garbage-collected should be marked with a cross with no lifeline after that.

The lifeline after that is an issue with PlantUML. We will note that below the diagram.

yentheng0110 · 2024-10-31T06:15:19Z

docs/DeveloperGuide.md

+<img src = "images/ArchitectureSequenceDiagram.png">
+
+The above **Sequence Diagram** shows how the different components of the system interact with one
+another in the scenario when the command `add -e event -t 1200 -v venue` is executed.


Perhaps you can add colons to indicate that these are actual instances/objects instead of classes. This comment applies to all other sequence diagrams throughout the DG too.

yentheng0110 · 2024-10-31T06:22:09Z

docs/DeveloperGuide.md

+* Load events and participants information from a text file and save it to `EventList` list.
+* Save events from `EventList` list to a text file


Perhaps can consider adding a sequence diagram to illustrate the method calls here (similar to how you created a sequence diagram for the command component)
Same goes to the event component

yentheng0110 · 2024-10-31T06:23:48Z

docs/DeveloperGuide.md

+
+This section describes some noteworthy details on how certain features are implemented.
+
+### List feature[TBD]


Perhaps can write [Proposed] for proposed implementation of list feature instead of using abbreviations such as TBD which may not be easily understood by everyone

yentheng0110 · 2024-10-31T06:30:48Z

docs/DeveloperGuide.md

+**Add Event**
+
+<img src = "images/AddEventSequenceDiagram.png">
+
+**Add Participant**
+
+<img src = "images/AddParticipantSequenceDiagram.png">


The sequence diagram font size is too small relative to the font size of the main text. Perhaps you can consider making the two font sizes match?

We believe it's more of an issue of the sequence diagram being too large and complicated. We're planning to redo the diagram (other comments pointed out more pressing issues) so we'll take your point into account.

yentheng0110 · 2024-10-31T06:38:51Z

docs/DeveloperGuide.md

+
+The interactions between components during the execution of the `mark` command are show in the **Sequence Diagram** below:
+
+<img src = "images/MarkEventSequenceDiagram.png">


I think the boolean variable toMark can be renamed to sound like booleans (such as isDone) so that there is no coding standard violations

yentheng0110 · 2024-10-31T06:40:42Z

docs/DeveloperGuide.md

@@ -4,30 +4,274 @@

 {list here sources of all reused/adapted ideas, code, documentation, and third-party libraries -- include links to the original source as well}


Perhaps can consider removing the acknowledgements section if you don't have sources to acknowledge

Noted, thanks for pointing this out!

Update code flow to be consistent throughout

Add Edit feature to UG

Add Edit feature to DG

Update FilterCommand , UG and DG

Update output string method

Update DG manual testing section to reflect actual functionality

Add project management items to PPP

Add page break before "Features" section of UG

Convert command list in UG to screenshot

Resolve storage bugs

Only use english keyboard

Update regex

Update Storage

Update storage loading sequence diagram

Update Storage PUML

Mahesh1772 reviewed Oct 27, 2024

View reviewed changes

TVageesan reviewed Oct 30, 2024

View reviewed changes

DarkDragoon2002 reviewed Oct 30, 2024

View reviewed changes

averageandyyy reviewed Oct 31, 2024

View reviewed changes

yentheng0110 reviewed Oct 31, 2024

View reviewed changes

jemehgoh and others added 25 commits November 5, 2024 16:46

Merge pull request #161 from KuanHsienn/Code-Flow

c0d4d92

Update code flow to be consistent throughout

Update kuanhsienn.md

3e9c624

Update kuanhsienn.md

ec57e67

Add Javadocs for getParticipants and getItems method

96e337b

Merge branch 'master' into command-javadoc

76702ce

Consolidate index out of bounds exception handling

a3dfa13

Update UserGuide.md

facc333

Update MenuCommand.java

bb1b843

Update EXPECTED.TXT

904592e

Update EXPECTED.TXT

78e6402

add some detailed information

7c29014

add some details

d66b9d7

Merge branch 'master' into UG-Edit

24ceec5

Merge pull request #155 from MatchaRRR/UG-Edit

915c42c

Add Edit feature to UG

Update Javadocs

ccf7db6

Move date-time and priority exception handling up to parseCommand

aa0ab83

Extract magic strings from mark command

10659b9

Update shadowJar name in line with manual testing

62b92ea

Edit method names for filtering by name

8e53e66

Update developer guide with updated filter command

50a61e7

Update user guide with updated filter command

844b002

Edit order of declared variables

584d062

Merge pull request #154 from MatchaRRR/DG_diagram

0ad5fab

Add Edit feature to DG

Merge pull request #164 from glenn-chew/FilterBranch

29639b3

Update FilterCommand , UG and DG

Fix user guide bugs

7fba40b

KuanHsienn and others added 30 commits November 11, 2024 22:10

Resolve duplicate flag at the end bug

dfa8d0d

Update manual testing section to reflect actual functionality

0f5696d

Update output string method

f3a0a4a

Update EXPECTED.TXT

4e39219

Add code tags to list command section and update homepage image

6ead99d

Merge pull request #268 from LTK-1606/MessageFix

fb3b073

Update output string method

Merge pull request #269 from jemehgoh/manual-testing-fixes

07d351f

Update DG manual testing section to reflect actual functionality

Add project management items to PPP

bcb2d80

Merge pull request #270 from jemehgoh/ppp-amendment

4d89114

Add project management items to PPP

Add page break before "Features" section of UG

32de0a7

Merge pull request #271 from jemehgoh/ug-break

2242c5e

Add page break before "Features" section of UG

Convert command list in UG to screenshot

4519223

Merge pull request #272 from jemehgoh/ug-diagram-fix

591b9e8

Convert command list in UG to screenshot

Resolve bug in loading when datetime field in text file is edited

29333c2

Resolve bug in invalid mark status in storage file

b3ced77

Resolve bugs in invalid email in storage file

a1a1188

Resolve CI test

2daa585

Update UG

a73088e

Update regex

da79074

Merge pull request #273 from KuanHsienn/master

d10c890

Resolve storage bugs

Merge pull request #274 from LTK-1606/Keyboard

16aa6d8

Only use english keyboard

Merge pull request #275 from LTK-1606/Regex

fab3360

Update regex

Update error handling

526ae1f

Update output message

0cd9e9b

Merge pull request #276 from LTK-1606/Storage

e1240e4

Update Storage

Update storage loading sequence diagram

27a3eaf

Update image

c251b73

Merge pull request #277 from LTK-1606/Storage

8b07b4a

Update storage loading sequence diagram

Update Storage PUML

2ab6067

Merge pull request #278 from KuanHsienn/master

2670eb1

Update Storage PUML

		2. The user enters the command `mark -e Event 1 -s done` to mark `Event 1` as done. `MarkEventCommand` calls `MarkEventCommand#execute`,
		in which it gets the event `Event 1` from the event list, and sets its mark status to `true` or done.

		It uses the `String.format` method with `LIST_MESSAGE` to include the total number of events in the message header.
		Events are appended to `outputMessage` with numbered formatting for readability.


		Given below is an example usage scenario for the `add` mechanism, and how it behaves at each step.

		1. The user enters the command `add` followed by `-e` or `-p` to indicate adding an event or participant.


		### Storage component

		<img src = "images/StorageClassDiagram.png">


		The `Command` component and its component classes are shown in the below Class Diagram:

		<img src = "images/CommandClassDiagram.png">

		The interactions between `Command` and other commands in the system is shown in the following _Sequence Diagram_:

		<img src = "images/CommandSequenceDiagram.png">


		The `Event` component and its component classes are shown in the below Class Diagram:

		<img src = "images/EventClassDiagram.png">

		Add Participant

		<img src = "images/AddParticipantSequenceDiagram.png">


		Remove Participant

		<img src = "images/RemoveParticipantSequenceDiagram.png">


		The interactions between components during the execution of the `view` command are show in the Sequence Diagram below:

		<img src = "images/ViewEventSequenceDiagram.png">


		The interactions between components during the execution of the `mark` command are show in the Sequence Diagram below:

		<img src = "images/MarkEventSequenceDiagram.png">


		### Interactions between components

		<img src = "images/ArchitectureSequenceDiagram.png">

		* Load events and participants information from a text file and save it to `EventList` list.
		* Save events from `EventList` list to a text file


		This section describes some noteworthy details on how certain features are implemented.

		### List feature[TBD]

		@@ -4,30 +4,274 @@

		{list here sources of all reused/adapted ideas, code, documentation, and third-party libraries -- include links to the original source as well}

[CS2113-W13-3] EventManagerCLI #7

Are you sure you want to change the base?

[CS2113-W13-3] EventManagerCLI #7

Conversation

KuanHsienn commented Sep 18, 2024

Mahesh1772 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

Choose a reason for hiding this comment

Choose a reason for hiding this comment

DarkDragoon2002 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

averageandyyy left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yentheng0110 Oct 31, 2024 • 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

jemehgoh Oct 31, 2024 • 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

yentheng0110 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yentheng0110 Oct 31, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

yentheng0110 Oct 31, 2024 • 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

yentheng0110 Oct 31, 2024 •

edited

Loading

jemehgoh Oct 31, 2024 •

edited

Loading

yentheng0110 Oct 31, 2024 •

edited

Loading

yentheng0110 Oct 31, 2024 •

edited

Loading