Add latest comments block #7941

tofumatt · 2018-07-12T21:38:10Z

Description

Fixes #1792. Note that this PR is based on #7369, which is based on #1931. I've made a few tweaks (mentioned in #7369).

Closes #7369.

I've made some changes here from the original PR, mainly around:

changing get_the_title to _draft_or_post_title as it's the only way to display posts with no title
escaping the post title
Markup changes
CSS refactors/tweaks
Added centre-alignment support

I was going to add tests but these tests require post comments, and making them means I need a mock/test database, as the current e2e tests run against the local development URL. I'll do those in a follow-up branch as I've tested this locally a fair bit.

Adds Latest Comments block v1 using ServerSideRender component.
Allows configuring the following:

Number of comments displayed;
Comment excerpt to be shown;
Permit avatar to be shown;
Permit timestamps to be shown.

Screenshots

Editor:

Frontend:

Checklist:

My code is tested functionally.
My code follows the WordPress code style.
My code has proper inline documentation.

tofumatt · 2018-07-12T21:39:24Z

core-blocks/latest-comments/index.php

+			}
+
+			$list_items_markup .= __( ' on ', 'gutenberg' );
+			$list_items_markup .= '<a class="wp-block-latest-comments__comment-link" href="' . esc_url( get_comment_link( $comment ) ) . '">' . get_the_title( $comment->comment_post_ID ) . '</a>';


Just checked into this and it looks like get_the_title() doesn't do any escaping, so this is Dangerous™. I'll have it fixed in a branch and add tests for it.

Soean · 2018-07-13T12:26:45Z

core-blocks/latest-comments/index.php

+		$attributes['commentsToShow'] = $DEFAULT_COMMENTS_TO_SHOW;
+	}
+
+	// This filter is documented in wp-includes/widgets/class-wp-widget-recent-comments.php


Inline comments must end in full-stops, exclamation marks, or question marks

Soean · 2018-07-13T12:27:27Z

core-blocks/latest-comments/index.php

+				$author_markup .= '<span class="wp-block-latest-comments__comment-author">' . get_comment_author( $comment ) . '</span>';
+			}
+
+			$post_title = '<a class="wp-block-latest-comments__comment-link" href="' . esc_url( get_comment_link( $comment ) ) . '">' . esc_html ( _draft_or_post_title( $comment->comment_post_ID ) ) . '</a>';


There is a space after esc_html

Soean · 2018-07-13T12:30:23Z

core-blocks/latest-comments/index.php

+
+			$list_items_markup .= sprintf(
+				/* translators: 1: author name (inside <a> or <span> tag, based on if they have a URL), 2: post title related to this comment */
+				__( '%1$s on %2$s' ),


Text domain ''gutenberg' is missing

Soean · 2018-07-13T12:33:55Z

core-blocks/latest-comments/edit.js

+							onChange={ this.toggleAttribute( 'displayAvatar' ) }
+						/>
+						<ToggleControl
+							label={ __( 'Display date/time' ) }


I only see the date, no time

Huh, seems right. It used to say "timestamp" which is definitely wrong, but maybe it should be using a better date function. I'll check it out...

Soean · 2018-07-13T12:59:07Z

core-blocks/latest-comments/index.php

+// appearing with no title.
+require_once( ABSPATH . 'wp-admin/includes/template.php' );
+
+$DEFAULT_COMMENTS_TO_SHOW = 5;


This is not valid for phpcs, see: https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/#naming-conventions

Soean · 2018-07-13T13:01:12Z

core-blocks/latest-comments/index.php

+}
+
+register_block_type( 'core/latest-comments', array(
+	'attributes' => array(


PHPCS warnings, see https://travis-ci.org/WordPress/gutenberg/jobs/403535665

Ah, cheers. They looked weird before with bizarre indentation but I guess that was the right way.

Yes, it looks a little bit strange.
You can check it local: https://wordpress.org/gutenberg/handbook/reference/coding-guidelines/#php

tofumatt · 2018-07-16T19:44:27Z

(I think this is all set for another review.)

mcsf

Thanks for taking this on, @tofumatt.

We need to address the case in which there are no comments to show. This is what the user gets now:

mcsf · 2018-07-17T16:14:32Z

core-blocks/latest-comments/edit.js

+	setCommentsToShow( commentsToShow ) {
+		const { setAttributes } = this.props;
+
+		setAttributes( { commentsToShow: parseInt( commentsToShow, 10 ) || 0 } );


Type coercion already happens behind the block API (asType). We should drop the ad hoc validation here. See Gallery or Columns for examples of core blocks using RangeControl with no other type validation than the one built in.

I'm not a big fan of setAlignment and setCommentsToShow, as they just duplicate setAttributes.

I also don't love toggleAttribute, but don't feel strongly enough to oppose.

The Gallery block, for instance, has a lot of specific functions that just call setAttributes. I think the notion is explicitly setting one prop per control. It's usually the way I'd create functions for a component. 🤷‍♂️

The alternative is an inline function passed as a prop, right?

<RangeControl label={ __( 'Number of comments' ) } value={ commentsToShow } onChange={ this.setCommentsToShow } min={ MIN_COMMENTS } max={ MAX_COMMENTS } />

or

<RangeControl label={ __( 'Number of comments' ) } value={ commentsToShow } onChange={ ( value ) => ( this.setAttributes( 'commentsToShow', value ) ) } min={ MIN_COMMENTS } max={ MAX_COMMENTS } />

Hm, in both I only see drawbacks. 😄 Pick your poison, I say.

mcsf · 2018-07-17T16:57:46Z

core-blocks/latest-comments/editor.scss

+	a {
+		cursor: default;
+		pointer-events: none;
+	}


This poses the same interaction problems as when the Archives block was being developed. We should use the more robust Disabled element. See 480338c

Nice, I didn't code this bit but will do. 👍

mcsf · 2018-07-17T16:58:19Z

core-blocks/latest-comments/index.js

+		}
+	},
+
+	edit: edit,


(minor): edit,

I think we should have an eslint rule for that if it's important, but I'll change this one. 😄

Nop, totally minor. I prefer the shorthand. ¯_(ツ)_/¯

I do too… but we should have rules over preferences 😉

I've filed #8009.

mcsf · 2018-07-17T16:59:30Z

core-blocks/latest-comments/index.js

+	getEditWrapperProps( attributes ) {
+		const { align } = attributes;
+
+		if ( DEFAULT_CONTROLS.includes( align ) ) {


I realize that the way we need to wrangle alignment types and do the getEditWrapperProps dance is suboptimal, but I'd rather have that addressed separately. Can we keep getEditWrapperProps here in line with other core blocks and revert exposing the constants?

Related is
#7908 (comment); before this the code copied what many other elements did and ignored centre-alignment, which caused the centre alignment option to do nothing.

I feel like it's better to do this as a starting point here and convert everything else over in #7908. This would be the way we'd want things to go, right?

This would be the way we'd want things to go, right?

Maybe, maybe not. :) But it deserves its own PR. I'd undo here.

mcsf · 2018-07-17T17:00:26Z

core-blocks/latest-comments/index.js

+/**
+ * Internal dependencies.
+ */
+import { DEFAULT_CONTROLS } from 'editor/components/block-alignment-toolbar';


Per my other comment, we should get rid of this, but worth noting that this would've been a disapproved import (importing private entities across packages).

I think I'm lost–how is it a private entity?

Because it's not a top-level export of editor, i.e. you wouldn't be able to get it via

import { DEFAULT_CONTROLS } from '@wordpress/editor';

and we avoid importing across blocks in any other fashion (i.e. a module in core-blocks importing from editor). There were some exceptions to this due to circular dependencies, but I think they're all but solved.

Aha, gotcha.

Has there been discussion about a custom rule to catch that for us or has it been difficult to implement? Seems quite easy to miss in a review.

There are rules against import { Bla } from 'editor'; (and any other package), but none for deep access. I'm assuming we don't yet forbit deep access because of those unresolved circular dependencies we had-and-may-still-have. Someone may correct me on this. :)

That won't actually work (eslint throws an error), but I have a PR incoming.

That won't actually work (eslint throws an error), but I have a PR incoming.

Yeah, might be the same thing I've encountered before, where it was solved by including the unicode equivalent character of the slash.

Uncanny! Do you have a matcher for lint?

I actually have no idea how this notification came through to my inbox 😅

Whoa, is that what that is? If it works I'll add a comment for it this time 😅

zomg that worked, thanks. I'll add it and add a comment this time 😉

mcsf · 2018-07-17T17:03:55Z

core-blocks/latest-comments/index.php

+				$author_markup .= '<span class="wp-block-latest-comments__comment-author">' . get_comment_author( $comment ) . '</span>';
+			}
+
+			$post_title = '<a class="wp-block-latest-comments__comment-link" href="' . esc_url( get_comment_link( $comment ) ) . '">' . esc_html( _draft_or_post_title( $comment->comment_post_ID ) ) . '</a>';


_draft_or_post_title already calls esc_html, though I can accept if you'd rather also escape here for reviewers peace of mind.

I think I originally added the esc_html (or it was here already?) because we weren't using _draft_or_post_title. I suppose now that it's being used we can omit the extra escape.

In general I like seeing it but in this case I'll leave a comment explaining that _draft_or_post_title does the escaping. No need to run it twice.

tofumatt · 2018-07-17T17:09:39Z

Yeah, I noticed that and I have something in the pipeline, should be pushed soon.

tofumatt · 2018-07-17T19:48:05Z

Thanks for the review, all set for another look.

See: #7941 (comment)

tofumatt · 2018-07-17T19:57:17Z

Wait, scratch that, I seem to be getting a weird CSS error locally. Investigating...

* chore: Improve eslint checks for deep imports See: #7941 (comment) * chore: Use fetch not request

tofumatt · 2018-07-17T20:30:36Z

Wait, scratch that, I seem to be getting a weird CSS error locally. Investigating...

It was something weird locally. Reset my env and everything is good. Ready for another review!

aduth · 2018-07-18T18:34:18Z

Can #7369 be closed in favor of this one?

aduth · 2018-07-18T18:37:20Z

Got some test failures, might be a bad rebase with the fixtures. Should be regenerated with npm run fixtures:regenerate.

tofumatt · 2018-07-18T18:43:20Z

Indeed, I see those too. Just a moment and I'll push that 👍

tofumatt · 2018-07-18T19:26:57Z

Well, fixed things manually for now, but I'll need to see why the fixtures aren't regenerating properly later... Should be passing now.

aduth · 2018-07-19T12:27:21Z

There are PHPCS (code styling) errors now. Will review what's here currently in the meantime.

FILE: /app/core-blocks/latest-comments/index.php
----------------------------------------------------------------------
FOUND 2 ERRORS AFFECTING 1 LINE
----------------------------------------------------------------------
 114 | ERROR | [x] Expected 1 spaces after opening bracket; 0 found
     |       |     (PEAR.Functions.FunctionCallSignature.SpaceAfterOpenBracket)
 114 | ERROR | [x] Expected 1 spaces before closing bracket; 0 found
     |       |     (PEAR.Functions.FunctionCallSignature.SpaceBeforeCloseBracket)

tofumatt · 2018-07-19T12:33:37Z

Shoot, I thought I fixed them, sorry 'bout that. Will push the fix now.

tofumatt · 2018-07-19T12:34:30Z

(Fixed)

aduth · 2018-07-19T12:28:39Z

core-blocks/latest-comments/edit.js

+		this.toggleAttribute = this.toggleAttribute.bind( this );
+	}
+
+	toggleAttribute( propName ) {


This function doesn't toggle anything on its own, it creates a function which performs the toggle. More accurately, it might be named createToggleAttribute.

aduth · 2018-07-19T12:29:49Z

core-blocks/latest-comments/edit.js

+						<ToggleControl
+							label={ __( 'Display avatar' ) }
+							checked={ displayAvatar }
+							onChange={ this.toggleAttribute( 'displayAvatar' ) }


toggleAttribute returns a new function every invocation, causing React to do render reconciliation more often than we need it to. I wonder if we should pre-bind these functions in the constructor:

constructor() { // ... this.toggleDisplayAvatar = this.createToggleAttribute( 'displayAvatar' ); }

Yeah, this has been pointed out elsewhere that this pattern is bad for unneeded re-renders, though obviously the code is nice.

Pre-binding them in the constructor is a good pattern actually 👍

aduth · 2018-07-19T12:30:26Z

core-blocks/latest-comments/edit.js

+ */
+import './editor.scss';
+
+const MIN_COMMENTS = 1;


IMO we should JSDoc any constant, even just to establish the convention in encouraging the practice for less-obvious constants.

I'm cool with that 👍

aduth · 2018-07-19T12:31:14Z

core-blocks/latest-comments/edit.js

+						/>
+					</PanelBody>
+				</InspectorControls>
+				<Disabled>


Makes me wonder: Is there any case where we want ServerSideRender to not be disabled? Should this be built-in to the render logic of that component?

I wondered that too, we should probably open an issue for it. I suppose building it in and then having some escape hatch prop that doesn't disable it would be good.

aduth · 2018-07-19T12:31:41Z

core-blocks/latest-comments/editor.scss

+	margin-right: 10px;
+}
+
+.edit-post-visual-editor {


Why do we need this context?

I bet we don't; I inherited this CSS and I guess I didn't refactor enough. It can go. 👍

aduth · 2018-07-19T12:34:59Z

core-blocks/latest-comments/index.php

+// appearing with no title.
+require_once( ABSPATH . 'wp-admin/includes/template.php' );
+
+$default_comments_to_show = 5;


As I understand it, scoping in PHP won't work as expected with what we have here. This would need to be accessed by global, which we're not doing.

Simpler demonstration:

Before:

<?php $extra = 'bar'; function do_foo() { echo 'foo' . $extra; } do_foo();

⇒ php test.php foo%

After:

<?php $extra = 'bar'; function do_foo() { global $extra; echo 'foo' . $extra; } do_foo();

⇒ php test.php foobar%

Though, as written, it's more of a constant, which is exemplified in define.

Though, above all, does this really need to be in the global scope? I think we're over-optimizing at the risk of outside breakage (anything else in the running WordPress page could access this variable, intentionally or not).

Yeah I didn't think using define was right because I wanted a constant scoped to this file–and the constants created by define are global... right?

I'll admit that my PHP is wildly rusty and I'm totally unclear what the best practice is for this.

I just want a file-scoped constant. I can remove it if that's a pain to make.

and the constants created by define are global... right?

Yes, and so is the previous variable assignment, as can be demonstrated:

diff --git a/core-blocks/latest-comments/index.php b/core-blocks/latest-comments/index.php index 33c21e41f..092fe08eb 100644 --- a/core-blocks/latest-comments/index.php +++ b/core-blocks/latest-comments/index.php @@ -9,6 +9,7 @@ // appearing with no title. require_once( ABSPATH . 'wp-admin/includes/template.php' ); +$default_comments_to_show = 5; define( 'GUTENBERG_LATEST_COMMENTS_BLOCK_DEFAULT_TO_SHOW', 5 ); /** diff --git a/lib/load.php b/lib/load.php index f1a8b09c6..f8a4b7985 100644 --- a/lib/load.php +++ b/lib/load.php @@ -34,3 +34,5 @@ require dirname( __FILE__ ) . '/register.php'; foreach ( glob( dirname( __FILE__ ) . '/../core-blocks/*/index.php' ) as $block_logic ) { require $block_logic; } + +var_export( $default_comments_to_show ); exit;

Related: http://php.net/manual/en/language.variables.scope.php

Yeah, I didn't realise that 😢

If the define call is too global I'm fine with just hard-coding it in. 🤷‍♂️

Since it's prefixed enough it shouldn't be a huge concern.

Alternatively, we could consider enhancing our JSON schema support to handle minimum and maximum, rely on the validation behavior, and assign the default only once in the block registration.

https://spacetelescope.github.io/understanding-json-schema/reference/numeric.html#range

In fact, since we use REST validation under the hood, I wonder if this is already possible.

It's already supported:

https://github.com/WordPress/wordpress-develop/blob/8f95800d52c1736d651ae6e259f90ad4a0db2c3f/src/wp-includes/rest-api.php#L1169-L1209

Our usage will trigger the default to take its place when outside bounds:

gutenberg/lib/class-wp-block-type.php

Lines 137 to 146 in 348e463

if ( isset( $attributes[ $attribute_name ] ) ) {

$is_valid = rest_validate_value_from_schema( $attributes[ $attribute_name ], $schema );

if ( ! is_wp_error( $is_valid ) ) {

$value = rest_sanitize_value_from_schema( $attributes[ $attribute_name ], $schema );

}

}

if ( is_null( $value ) && isset( $schema['default'] ) ) {

$value = $schema['default'];

}

There's also enum to take care of the align valid options:

https://github.com/WordPress/wordpress-develop/blob/8f95800d52c1736d651ae6e259f90ad4a0db2c3f/src/wp-includes/rest-api.php#L1120-L1125

https://spacetelescope.github.io/understanding-json-schema/reference/generic.html#enumerated-values

Huh, nice! Okay, I'll look at that.

tofumatt · 2018-07-19T14:24:08Z

Thanks! Ready for another review.

aduth · 2018-07-19T15:55:52Z

core-blocks/latest-comments/index.js

+
+		// TODO: Use consistent values across the app;
+		// see: https://github.com/WordPress/gutenberg/issues/7908.
+		if ( [ 'left', 'center', 'right', 'wide', 'full' ].includes( align ) ) {


We should double check that our new ES2015 prototype member polyfills with Babel 7 useBuiltIns: 'usage' allows this to work as expected in IE11.

This is an ES2015+ method which until recently was not expected to be polyfilled and would therefore error in IE11.

I tested it in IE11 and it worked; I could change the align values and nothing errored on me (it touches this code path).

aduth · 2018-07-19T17:33:54Z

core-blocks/latest-comments/index.php

+// appearing with no title.
+require_once( ABSPATH . 'wp-admin/includes/template.php' );
+
+$default_comments_to_show = 5;


This $default_comments_to_show variable is unused. I suspect it wasn't intentional to keep.

Entirely not, sorry. Fixed.

tofumatt · 2018-07-19T17:38:34Z

Side note: I have e2e tests written and ready for this, but they depend on #8041 because I need to ensure there are no existing posts/comments in the test database.

aduth

Looks good 👍

Stale review.

StaggerLeee · 2018-07-20T19:31:35Z

One question. Who will use it ?
It is not anything for the Post. Latest comments is thing for Widget, sidebar.

I am bit confuse with your plans to make blocks for all old WP native widgets.

tofumatt · 2018-07-20T21:11:43Z

The future is blocks :-) The long-term plan is to have all pieces of a site be built using blocks, so a block like this (or latest posts) can be using where a widget used to go. - Matt (Sent from mobile)

…

On 20 Jul 2018, at 20:31, StaggerLeee ***@***.***> wrote: One question. Who will use it ? It is not anything for the Post. Latest comments is thing for Widget. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.

tofumatt commented Jul 12, 2018

View reviewed changes

tofumatt requested a review from gziolo July 12, 2018 22:37

Soean added the New Block Suggestion for a new block label Jul 13, 2018

tofumatt requested a review from a team July 13, 2018 12:30

Soean reviewed Jul 13, 2018

View reviewed changes

tofumatt added this to the 3.3 milestone Jul 13, 2018

Soean reviewed Jul 13, 2018

View reviewed changes

mcsf previously requested changes Jul 17, 2018

View reviewed changes

This was referenced Jul 17, 2018

Alignment: blocks using alignment should apply data-align consistently #7908

Closed

eslint rule for object property shorthand/object-shorthand #8009

Closed

tofumatt mentioned this pull request Jul 17, 2018

chore: Improve eslint checks for deep imports #8013

Merged

tofumatt requested a review from mcsf July 17, 2018 19:47

tofumatt added a commit that referenced this pull request Jul 17, 2018

chore: Improve eslint checks for deep imports

3044e5f

See: #7941 (comment)

tofumatt force-pushed the miina-add/latest-comments-block branch from aa2bed3 to 6604304 Compare July 17, 2018 19:55

tofumatt added a commit that referenced this pull request Jul 17, 2018

chore: Improve eslint checks for deep imports (#8013)

d17effe

* chore: Improve eslint checks for deep imports See: #7941 (comment) * chore: Use fetch not request

aduth mentioned this pull request Jul 18, 2018

Add Latest Comments block. #7369

Closed

3 tasks

miina added 3 commits July 18, 2018 19:43

Start adding latest comments block.

f35aaa9

Separate edit.js file. Add style

8492bdf

Fix style. Fix displaying controls.

8d92df9

Fix test fixtures

6bc741a

tofumatt mentioned this pull request Jul 19, 2018

chore: Isolate e2e tests and reset them for each run #8041

Merged

chore: Fix PHPCS error

a59a647

aduth requested changes Jul 19, 2018

View reviewed changes

chore: Improve rendering and other PR tweaks

dfc09c1

tofumatt requested review from aduth and a team July 19, 2018 14:23

aduth reviewed Jul 19, 2018

View reviewed changes

Use validation built-in to blocks

49441d7

aduth requested changes Jul 19, 2018

View reviewed changes

Oops

0d4e583

tofumatt requested a review from aduth July 19, 2018 17:38

aduth approved these changes Jul 19, 2018

View reviewed changes

Sigh

28ac484

tofumatt merged commit 1feed2c into master Jul 19, 2018

tofumatt deleted the miina-add/latest-comments-block branch July 19, 2018 18:13

tofumatt mentioned this pull request Jul 20, 2018

fix: Latest comment admin imports #8085

Merged

pento mentioned this pull request Jul 23, 2018

Fix the Server Fixtures generator #8126

Closed

4 tasks

afercia mentioned this pull request Jan 30, 2019

Widget-block Screen in wp-admin #13204

Closed

afercia added the [Feature] Widgets Screen The block-based screen that replaced widgets.php. label Jan 30, 2019

	if ( isset( $attributes[ $attribute_name ] ) ) {
	$is_valid = rest_validate_value_from_schema( $attributes[ $attribute_name ], $schema );
	if ( ! is_wp_error( $is_valid ) ) {
	$value = rest_sanitize_value_from_schema( $attributes[ $attribute_name ], $schema );
	}
	}

	if ( is_null( $value ) && isset( $schema['default'] ) ) {
	$value = $schema['default'];
	}

Add latest comments block #7941

Add latest comments block #7941

Conversation

tofumatt commented Jul 12, 2018 • edited Loading

Description

Screenshots

Editor:

Frontend:

Checklist:

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

tofumatt commented Jul 16, 2018

mcsf 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

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

tofumatt commented Jul 17, 2018

tofumatt commented Jul 17, 2018

tofumatt commented Jul 17, 2018

tofumatt commented Jul 17, 2018

aduth commented Jul 18, 2018

aduth commented Jul 18, 2018

tofumatt commented Jul 18, 2018

tofumatt commented Jul 18, 2018

aduth commented Jul 19, 2018 • edited Loading

tofumatt commented Jul 19, 2018

tofumatt commented Jul 19, 2018

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

aduth Jul 19, 2018 • 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

aduth Jul 19, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tofumatt commented Jul 19, 2018

tofumatt commented Jul 12, 2018 •

edited

Loading

aduth commented Jul 19, 2018 •

edited

Loading

aduth Jul 19, 2018 •

edited

Loading

aduth Jul 19, 2018 •

edited

Loading

StaggerLeee commented Jul 20, 2018 •

edited

Loading