Implement `remark` command #599

yamgent · 2017-07-30T09:37:00Z

Part of #784.

Proposed merge commit message:

The PersonCard stores basic personal information about a contact, by
providing fields such as Name, Email, Address, Phone and Tags.

There are no fields present in a PersonCard for the user to add
additional comments about a contact, that may not suit any of the
existing fields.

Let's implement a `remark` command so that the user can add additional
comments about a contact.

Note: For demo purpose, don't merge this to master!

mention-bot · 2017-07-30T09:37:01Z

@yamgent, thanks for your PR! By analyzing the history of the files in this pull request, we identified @Zhiyuan-Amos, @edmundmok and @eugenepeh to be potential reviewers.

CanIHasReview-bot · 2018-02-04T07:32:24Z

v1

@yamgent submitted v1 for review.

[v1 1/9] Logic: Teach the app to accept 'remark' but do nothing
[v1 2/9] Logic: Teach the app to accept 'remark' arguments but still do nothing
[v1 3/9] Ui: Add a placeholder for remark in PersonCard GUI
[v1 4/9] Model: Add Remark class
[v1 5/9] Model: Modify `Person` to support a `Remark` field
[v1 6/9] Storage: Add Remark field to XmlAdaptedPerson class
[v1 7/9] Test: Add withRemark() for PersonBuilder
[v1 8/9] Ui: Connect Remark field to PersonCard
[v1 9/9] Logic: Implement RemarkCommand execute() logic

(📚 Archive)

Checkout this PR version locally

git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/599/1/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

Zhiyuan-Amos

[1/9]

Zhiyuan-Amos · 2018-02-07T00:43:44Z

src/test/java/seedu/address/logic/parser/AddressBookParserTest.java

+    @Test
+    public void parseCommand_remark() throws Exception {
+        RemarkCommand command = (RemarkCommand) parser.parseCommand(RemarkCommand.COMMAND_WORD);
+        assertTrue(command instanceof RemarkCommand);


if you have forced cast it in the previous line, then this must definitely be an instance of RemarkCommand right? :P

Zhiyuan-Amos

[2/9]

Zhiyuan-Amos · 2018-02-07T00:45:41Z

src/main/java/seedu/address/logic/commands/RemarkCommand.java

+
+    /**
+     * @param index of the person in the filtered person list to edit the remark
+     * @param remark of the person


can be clearer: remark of the person to be updated to?

Zhiyuan-Amos · 2018-02-07T00:47:08Z

src/main/java/seedu/address/logic/parser/RemarkCommandParser.java

+public class RemarkCommandParser implements Parser<RemarkCommand> {
+    /**
+     * Parses the given {@code String} of arguments in the context of the RemarkCommand
+     * and returns an RemarkCommand object for execution.


Should we have {@code } to wrap around RemarkCommand?

Zhiyuan-Amos · 2018-02-07T00:53:22Z

src/test/java/seedu/address/logic/commands/RemarkCommandTest.java

+        // different index -> returns false
+        assertFalse(standardCommand.equals(new RemarkCommand(INDEX_SECOND_PERSON, VALID_REMARK_AMY)));
+
+        // different remarks -> returns false


Zhiyuan-Amos · 2018-02-07T00:53:57Z

src/test/java/seedu/address/logic/commands/RemarkCommandTest.java

    }

    /**
-     * Returns an {@code RemarkCommand}.
+     * Returns an {@code RemarkCommand} with parameters {@code index} and {@code remark}


missing period at the end of the sentence :P

Zhiyuan-Amos · 2018-02-07T00:55:13Z

src/test/java/seedu/address/logic/parser/AddressBookParserTest.java

-        assertTrue(command instanceof RemarkCommand);
+        final String remark = "Some remark.";
+        RemarkCommand command = (RemarkCommand) parser.parseCommand(RemarkCommand.COMMAND_WORD + " "
+                + INDEX_FIRST_PERSON.getOneBased() + " " + PREFIX_REMARK + " " + remark);


Should there be a space between PREFIX_REMARK and remark?

Zhiyuan-Amos · 2018-02-07T00:56:17Z

src/test/java/seedu/address/logic/parser/RemarkCommandParserTest.java

+    private RemarkCommandParser parser = new RemarkCommandParser();
+
+    @Test
+    public void parse_indexSpecified_failure() throws Exception {


failure? :O the test code below says assertParseSuccess XD

Zhiyuan-Amos · 2018-02-07T00:58:22Z

src/test/java/seedu/address/logic/parser/RemarkCommandParserTest.java

+
+        // have remarks
+        Index targetIndex = INDEX_FIRST_PERSON;
+        String userInput = targetIndex.getOneBased() + " " + PREFIX_REMARK.toString() + " " + remark;


Is there a need for " " between PREFIX_REMARK and remark?

Zhiyuan-Amos · 2018-02-07T00:58:35Z

src/test/java/seedu/address/logic/parser/RemarkCommandParserTest.java

+    public void parse_indexSpecified_failure() throws Exception {
+        final String remark = "Some remark.";
+
+        // have remarks


should be singular: remark

Zhiyuan-Amos · 2018-02-07T00:58:43Z

src/test/java/seedu/address/logic/parser/RemarkCommandParserTest.java

+        RemarkCommand expectedCommand = new RemarkCommand(INDEX_FIRST_PERSON, remark);
+        assertParseSuccess(parser, userInput, expectedCommand);
+
+        // no remarks


Should be singular: remark

Zhiyuan-Amos · 2018-02-07T00:59:31Z

src/test/java/seedu/address/logic/parser/RemarkCommandParserTest.java

+    public void parse_noFieldSpecified_failure() throws Exception {
+        String expectedMessage = String.format(MESSAGE_INVALID_COMMAND_FORMAT, RemarkCommand.MESSAGE_USAGE);
+
+        // nothing at all


this comment seems unnecessary because the test name already mentions that there's no field specified.

Though I wonder if we should have a test where the remark is specified but not the index.

Zhiyuan-Amos

[3/9] commit message:

Modify PersonCardHandle so that future tests can take read the
remarks.

take read the remarks :O

Zhiyuan-Amos

[4/9]

Zhiyuan-Amos · 2018-02-07T01:05:46Z

src/test/java/seedu/address/logic/commands/RemarkCommandTest.java

@@ -36,10 +37,10 @@ public void execute() throws Exception {

    @Test
    public void equals() {
-        final RemarkCommand standardCommand = new RemarkCommand(INDEX_FIRST_PERSON, VALID_REMARK_AMY);
+        final RemarkCommand standardCommand = new RemarkCommand(INDEX_FIRST_PERSON, new Remark(VALID_REMARK_AMY));


how about let's change VALID_REMARK_AMY to type Remark instead?

Was just following the style of this though, maybe need to put constant somewhere else?

https://github.com/yamgent/addressbook-level4/blob/e94cf07b3a37a31a54050e9e47afd7b107f17167/src/test/java/seedu/address/logic/commands/CommandTestUtil.java#L35-L39

Zhiyuan-Amos · 2018-02-07T01:07:55Z

src/test/java/seedu/address/model/person/RemarkTest.java

+        // null -> returns false
+        assertFalse(remark.equals(null));
+
+        // different person -> returns false


different person.... you mean different remark XD

Zhiyuan-Amos

[5/9]

Zhiyuan-Amos · 2018-02-07T01:10:05Z

src/main/java/seedu/address/model/util/SampleDataUtil.java

@@ -20,22 +21,22 @@
    public static Person[] getSamplePersons() {
        return new Person[] {
            new Person(new Name("Alex Yeoh"), new Phone("87438807"), new Email("[email protected]"),
-                new Address("Blk 30 Geylang Street 29, #06-40"),
+                new Address("Blk 30 Geylang Street 29, #06-40"), new Remark(""),


Should we extract these out as EMPTY_REMARK?

Zhiyuan-Amos · 2018-02-07T01:13:26Z

src/test/data/XmlUtilTest/validAddressBook.xml

@@ -5,53 +5,62 @@
        <phone isPrivate="false">9482424</phone>
        <email isPrivate="false">[email protected]</email>
        <address isPrivate="false">4th street</address>
+        <remark isPrivate="false"></remark>


out of scope of this PR, but why do we have a isPrivate in our xml file XD

Seems like an old artifact that was inherited from the lower levels of addressbook (which does have private fields). I guess we can remove it (unless anyone wants to come up with some useful features for it :P).

We can create an issue and write:

"It takes approx 2 weeks of full time work to implement a new feature. Start at your own risk!" XD

Zhiyuan-Amos

[8/9]:

. Just modify PersonCard's constructor to add the new method.

i don't see the new method though :O

Also, concerning commit organisation, I'm wondering if we should squash this commit with [v1 3/9] Ui: Add a placeholder for remark in PersonCard GUI i.e. both of these commits will become 1 commit at [7/8]. This is because there's no need for us to update the Ui component at [3/9] (I think later commits are not dependent on it).

Zhiyuan-Amos

[9/9]

Zhiyuan-Amos · 2018-02-07T01:32:17Z

src/main/java/seedu/address/logic/commands/RemarkCommand.java

+     * {@code personToEdit}.
+     */
+    private String generateSuccessMessage(Person personToEdit) {
+        if (!remark.value.isEmpty()) {


I think we can ternary this:

String message = !remark.value.isEmpty() ? MESSAGE_ADD_REMARK_SUCCESS : MESSAGE_DELETE_REMARK_SUCCESS; return String.format(message, personToEdit);

Zhiyuan-Amos · 2018-02-07T01:32:31Z

src/main/java/seedu/address/logic/commands/RemarkCommand.java

+    }
+
+    /**
+     * Generate a command execution success message based on whether the remark is added to or removed from


Zhiyuan-Amos · 2018-02-07T01:32:50Z

src/test/java/seedu/address/logic/commands/RemarkCommandTest.java

@@ -55,7 +122,7 @@ public void equals() {
        // different index -> returns false
        assertFalse(standardCommand.equals(new RemarkCommand(INDEX_SECOND_PERSON, new Remark(VALID_REMARK_AMY))));

-        // different remarks -> returns false
+        // different descriptor -> returns false


:O descriptor??

Zhiyuan-Amos · 2018-02-07T01:36:54Z

src/test/java/seedu/address/logic/commands/RemarkCommandTest.java

@@ -28,11 +33,73 @@
    private Model model = new ModelManager(getTypicalAddressBook(), new UserPrefs());

    @Test
-    public void execute() throws Exception {
-        final String remark = "Some remark";
+    public void execute_addRemark_success() throws Exception {


we should specify unfiltered list i.e. addRemarkUnfilteredList because we have test cases for filteredList. Same for below.

Zhiyuan-Amos · 2018-02-07T01:37:48Z

src/test/java/seedu/address/logic/commands/RemarkCommandTest.java

-    public void execute() throws Exception {
-        final String remark = "Some remark";
+    public void execute_addRemark_success() throws Exception {
+        Person editedPerson = new PersonBuilder(model.getFilteredPersonList().get(INDEX_FIRST_PERSON.getZeroBased()))


Maybe we can assign the first person of the filtered list as a variable, so that in line 45, we don't have to call model.getFilteredPersonList().get(0). Same for tests below.

yamgent · 2018-02-08T08:23:19Z

Also, concerning commit organisation, I'm wondering if we should squash this commit with [v1 3/9] Ui: Add a placeholder for remark in PersonCard GUI i.e. both of these commits will become 1 commit at [7/8]. This is because there's no need for us to update the Ui component at [3/9] (I think later commits are not dependent on it).

I think the "strange" commit organization - having [v1 3/9] separate from [v1 8/9] - was to "prevent student fatigue" (i.e. if we do the merge as you proposed, then the student is not going to see any visible changes in the frontend for the first 6 commits, which might discourage them).

Hence the [v1 3/9] is just placed there for them to visualize how it is going to look like eventually, which hopefully will "excite" them to continue the work. Also we try to touch different areas of the application as early as possible, rather than strictly leaving the UI components to the last.

CanIHasReview-bot · 2018-02-09T05:14:24Z

v2

@yamgent submitted v2 for review.

[v2 1/9] Logic: Teach the app to accept 'remark' but do nothing
[v2 2/9] Logic: Teach the app to accept 'remark' arguments but still do nothing
[v2 3/9] Ui: Add a placeholder for remark in PersonCard GUI
[v2 4/9] Model: Add Remark class
[v2 5/9] Model: Modify `Person` to support a `Remark` field
[v2 6/9] Storage: Add Remark field to XmlAdaptedPerson class
[v2 7/9] Test: Add withRemark() for PersonBuilder
[v2 8/9] Ui: Connect Remark field to PersonCard
[v2 9/9] Logic: Implement RemarkCommand execute() logic

(📚 Archive) (📈 Interdiff between v1 and v2)

Checkout this PR version locally

git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/599/2/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

yamgent · 2018-08-18T14:21:05Z

There were a lot of PRs merged to master, and a substantial amount of architecture changes and code style changes. Apologies in advance if I didn't capture everything for the changelog below (the interdiff shall be the authoritative source):

Changed remark to modelRemark in XmlAdaptedPerson#toModelType()
Remove the use of this..
Adapted to the new execute() interface.
The way RemarkCommandTest was written was changed because execute() interface was changed. No more prepareCommand(), no more prepareUndo(), etc.
Remove uses of throws Exception because most the errors are now RuntimeExceptions.

pyokagan

Interdiff looks good.

pyokagan

Some comments on stuff I just noticed along the way

pyokagan · 2018-08-20T07:12:38Z

src/main/java/seedu/address/model/person/Remark.java

+public class Remark {
+
+    public static final String MESSAGE_REMARK_CONSTRAINTS =
+            "Person remarks can take any values, can even be blank";


No point adding this if it is not used.

pyokagan · 2018-08-20T07:13:18Z

src/test/java/seedu/address/logic/parser/RemarkCommandParserTest.java

+    public void parse_indexSpecified_success() {
+        // have remark
+        Index targetIndex = INDEX_FIRST_PERSON;
+        String userInput = targetIndex.getOneBased() + " " + PREFIX_REMARK.toString() + nonEmptyRemark;


No need for the toString

Zhiyuan-Amos

[2/9]

Zhiyuan-Amos · 2018-08-20T14:58:59Z

src/main/java/seedu/address/logic/commands/RemarkCommand.java

+     */
+    public RemarkCommand(Index index, String remark) {
+        requireNonNull(index);
+        requireNonNull(remark);


e747390#diff-870783b7261d1855391681c89164b118R55

We can use requireAllNonNull instead? :)

Zhiyuan-Amos · 2018-08-20T15:00:17Z

src/main/java/seedu/address/logic/parser/RemarkCommandParser.java

+        try {
+            index = ParserUtil.parseIndex(argMultimap.getPreamble());
+        } catch (IllegalValueException ive) {
+            throw new ParseException(String.format(MESSAGE_INVALID_COMMAND_FORMAT, RemarkCommand.MESSAGE_USAGE));


Following 69728c1, we should use chained exceptions.

Zhiyuan-Amos

[9/9]

Zhiyuan-Amos · 2018-08-20T15:04:40Z

src/main/java/seedu/address/logic/commands/RemarkCommand.java


    private final Index index;
    private final Remark remark;

+    private Person personToEdit;
+    private Person editedPerson;


I think there's no need for these fields now.

Zhiyuan-Amos · 2018-08-20T15:06:04Z

src/main/java/seedu/address/logic/commands/RemarkCommand.java

+        } catch (DuplicatePersonException dpe) {
+            throw new AssertionError("Changing target person's remark should not result in a duplicate");
+        } catch (PersonNotFoundException pnfe) {
+            throw new AssertionError("The target person cannot be missing");


Just to check, we're catching RuntimeExceptions that should not be happening? Also, should we use chained exceptions here too?

Yeah I keep forgetting about these, will remove it :S.

. Modify RemarkCommand to take in an Index and String for remark, and print those two parameters as the error message . Modify RemarkCommandTest to test the equals method . Add RemarkCommandParser that will know how to parse two arguments, one index and one with prefix 'r/' . Add RemarkCommandParserTest that will test different boundary values for RemarkCommandParser. . Modify AddressBookParser to use the newly implemented RemarkCommandParser . Modify AddressBookParserTest to ensure that what the user input generated the correct command.

. Add label with any random text inside PersonListCard.fxml . Add FXML annotation in PersonCard to tie the variable to the actual label. . Modify PersonCardHandle so that future tests can read the remarks in the cards.

. Add Remark to model component (copy from Address, remove the regex and rename accordingly). . Add test for Remark (to test the equals method). . Modify RemarkCommand to now take in a Remark instead of a String.

. Add `Person#getRemark()` . You may assume that the user will not be able to use the `add` and `edit` commands to modify the remarks field (i.e. the person will be created without a remark). . Modify `SampleDataUtil` to add remarks for the sample data. I recommend deleting your addressBook.xml after this step so that you can see the remarks field come to life in your application.

. Add a new method `withRemark()` for `PersonBuilder`. This method will create a new `Remark` for the person that it is currently building. . Try and use the method on any sample `Person` in `TypicalPersons`.

. Just modify PersonCard's constructor to add the new method. . For test, modify GuiTestAssert#assertCardDisplaysPerson(...) to compare the now-functioning remark label.

. Replace the error message with the actual logic to modify the remarks of a person. . Update `RemarkCommandTest` to test that the `execute()` logic works.

CanIHasReview-bot · 2018-08-21T08:06:27Z

v7

@yamgent submitted v7 for review.

[v7 1/9] Logic: Teach the app to accept 'remark' but do nothing
[v7 2/9] Logic: Teach the app to accept 'remark' arguments but still do nothing
[v7 3/9] Ui: Add a placeholder for remark in PersonCard GUI
[v7 4/9] Model: Add Remark class
[v7 5/9] Model: Modify `Person` to support a `Remark` field
[v7 6/9] Storage: Add Remark field to XmlAdaptedPerson class
[v7 7/9] Test: Add withRemark() for PersonBuilder
[v7 8/9] Ui: Connect Remark field to PersonCard
[v7 9/9] Logic: Implement RemarkCommand execute() logic

(📚 Archive) (📈 Interdiff between v6 and v7) (📈 Range-Diff between v6 and v7)

Checkout this PR version locally

git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/599/7/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

Zhiyuan-Amos

Changes requested were made :)

yamgent · 2018-08-21T12:48:05Z

Thanks for all the reviews! @Zhiyuan-Amos @pyokagan

damithc

Sorry, missed this earlier

yamgent closed this Jul 30, 2017

This was referenced Oct 11, 2017

Remark command limyongsong/main#5

Merged

Creating a new command: remark. Step-by-step instructions from developer guide CS2103AUG2017-T09-B4/main#12

Merged

yamgent added pr.Answer Pull request is answer for a tutorial in developer guide. Do not actually merge. s.Ongoing labels Feb 4, 2018

yamgent reopened this Feb 4, 2018

Zhiyuan-Amos mentioned this pull request Feb 4, 2018

Rebase PRs used in suggested programming tasks #784

Closed

yamgent force-pushed the getting-started-remark branch 3 times, most recently from b1fd577 to e94cf07 Compare February 4, 2018 07:22

CanIHasReview-bot added s.ToReview and removed s.Ongoing labels Feb 4, 2018

Zhiyuan-Amos reviewed Feb 7, 2018

View reviewed changes

Zhiyuan-Amos added s.Ongoing and removed s.ToReview labels Feb 7, 2018

yamgent force-pushed the getting-started-remark branch 4 times, most recently from 7491051 to c317ab9 Compare February 9, 2018 04:54

CanIHasReview-bot added s.ToReview and removed s.Ongoing labels Aug 18, 2018

yamgent requested review from a team and removed request for a team August 18, 2018 14:21

pyokagan approved these changes Aug 20, 2018

View reviewed changes

pyokagan reviewed Aug 20, 2018

View reviewed changes

Zhiyuan-Amos reviewed Aug 20, 2018

View reviewed changes

yamgent added s.Ongoing and removed s.ToReview labels Aug 21, 2018

yamgent added 8 commits August 21, 2018 15:52

Ui: Add a placeholder for remark in PersonCard GUI

3d5983b

. Add label with any random text inside PersonListCard.fxml . Add FXML annotation in PersonCard to tie the variable to the actual label. . Modify PersonCardHandle so that future tests can read the remarks in the cards.

Model: Add Remark class

ae53a78

. Add Remark to model component (copy from Address, remove the regex and rename accordingly). . Add test for Remark (to test the equals method). . Modify RemarkCommand to now take in a Remark instead of a String.

Storage: Add Remark field to XmlAdaptedPerson class

9bee27e

Test: Add withRemark() for PersonBuilder

b3a1c56

. Add a new method `withRemark()` for `PersonBuilder`. This method will create a new `Remark` for the person that it is currently building. . Try and use the method on any sample `Person` in `TypicalPersons`.

Ui: Connect Remark field to PersonCard

e841d50

. Just modify PersonCard's constructor to add the new method. . For test, modify GuiTestAssert#assertCardDisplaysPerson(...) to compare the now-functioning remark label.

Logic: Implement RemarkCommand execute() logic

8e446e8

. Replace the error message with the actual logic to modify the remarks of a person. . Update `RemarkCommandTest` to test that the `execute()` logic works.

yamgent force-pushed the getting-started-remark branch from b0e6488 to 8e446e8 Compare August 21, 2018 07:55

CanIHasReview-bot added s.ToReview and removed s.Ongoing labels Aug 21, 2018

yamgent requested a review from Zhiyuan-Amos August 21, 2018 08:06

Zhiyuan-Amos approved these changes Aug 21, 2018

View reviewed changes

yamgent requested a review from damithc August 21, 2018 12:48

damithc approved these changes Sep 3, 2018

View reviewed changes

yamgent removed the s.ToReview label Sep 3, 2018

damithc closed this Dec 11, 2020

Implement remark command #599

Implement remark command #599

Conversation

yamgent commented Jul 30, 2017 • edited Loading

mention-bot commented Jul 30, 2017

CanIHasReview-bot commented Feb 4, 2018

v1

Zhiyuan-Amos left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

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

Zhiyuan-Amos left a comment

Choose a reason for hiding this comment

Zhiyuan-Amos left a comment • 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

Zhiyuan-Amos left a comment • 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

Zhiyuan-Amos left a comment • edited Loading

Choose a reason for hiding this comment

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

yamgent commented Feb 8, 2018 • edited Loading

CanIHasReview-bot commented Feb 9, 2018

v2

yamgent commented Aug 18, 2018

pyokagan left a comment

Choose a reason for hiding this comment

pyokagan left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Zhiyuan-Amos left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

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

CanIHasReview-bot commented Aug 21, 2018

v7

Zhiyuan-Amos left a comment

Choose a reason for hiding this comment

yamgent commented Aug 21, 2018

damithc left a comment

Choose a reason for hiding this comment

Implement `remark` command #599

Implement `remark` command #599

yamgent commented Jul 30, 2017 •

edited

Loading

Zhiyuan-Amos left a comment •

edited

Loading

Zhiyuan-Amos left a comment •

edited

Loading

Zhiyuan-Amos left a comment •

edited

Loading

yamgent commented Feb 8, 2018 •

edited

Loading