FSE: Update blocks categories #43670

fullofcaffeine · 2020-06-25T03:24:26Z

Changes proposed in this Pull Request

Update the category names for FSE blocks. More details: pc6Uok-1b-p2 and here (second task listed in the issue).
Adds a helper function that is used to safely update category names while still supporting old environments
Fix the FSE Jest configuration for TypeScript. It was needed in order for to properly transpile the test and the helper function included in the changeset when they are consumed by Jest. I decided not to split this change in another PR for two reasons: it's small and it's directly related to the change here.

Related PRs

Jetpack blocks: Update blocks categories jetpack#16363
wpcom-blocks: https://github.com/Automattic/wpcom-blocks/pull/178
block-experiments: Update blocks categories block-experiments#110

TODO

Unit test for the helper function: the test itself is trivial, but I didn't add because I still need to learn more about how unit testing is done within calypso. I'll have a look at it soon.
Add support for TS for FSE tests.
Should we write tests to check that each block is assigned to the right category names depending on the set of categories? Not sure what is the testing policy for Calypso and what coverage we aim for. Any insights appreciated! (Jon said it's not needed)
Squash and rebase from master before merging

Outstanding questions

Do we need to do anything with the category of the old/deprecated posts-list-block? (More details in p1593038635493700-slack-cylon)

Testing instructions

Atomated tests

cd to wp-calypso/apps/full-site-editing and run yarn test:js.

To manually test the changes

Setup a simple FSE-enabled site and atomic ephemeral sites by following the instructions here: PCYsg-ly5-p2. Map it to your sandbox.
cd to wp-calypso/apps/full-site-editing and run yarn dev --sync to sync it to your sandbox.
Choose a theme that's compatible with FSE (i.e Exford)
Edit your home-page
Add a new block and search for the block you're testing. Verify it's in the right category.

Test the scenarios above in the following environments:**

Simple website in calypso
Simple website in wp-admin
Atomic website
Atomic website with Gutenberg plugin disabled

~~Note: If this PR gets approved and merged, then I'll remove the helper function and tests from here (including the installation/configuration of jest).~~

matticbot · 2020-06-25T03:24:27Z

Test live: https://calypso.live/?branch=update/fse-blocks-categories-collections

matticbot · 2020-06-25T03:24:55Z

This PR does not affect the size of JS and CSS bundles shipped to the user's browser.

Generated by performance advisor bot at iscalypsofastyet.com.

a8ci18n · 2020-06-25T03:30:00Z

apps/full-site-editing/full-site-editing-plugin/newspack-blocks/blog-posts-block-editor.js

@@ -31,7 +32,7 @@ addFilter(
 registerBlockType( blockName, {
 	...settings,
 	title: __( 'Blog Posts', 'full-site-editing' ),


ℹ️ String reuse speeds up translation and improves consistency. The following string might make a good alternative and has already been translated 80 times:
translate( 'Blog Posts' ) ES Score: 10
See 1 additional suggestions in the PR translation status page

matticbot · 2020-06-25T03:32:01Z

Caution: This PR affects files in the FSE Plugin on WordPress.com
Please ensure your changes work on WordPress.com before merging.

D45465-code has been created so you can easily test it on your sandbox. See this FieldGuide page about developing in the FSE Plugin for more info: PCYsg-ly5-p2

sirreal

Thanks for starting on this! I know it's a draft, I left some early thoughts.

apps/full-site-editing/full-site-editing-plugin/block-helpers.js

sirreal · 2020-06-25T16:12:39Z

apps/full-site-editing/full-site-editing-plugin/block-helpers.js

+export const hasLegacyCategory = getCategories().some( function ( category ) {
+	return category.slug === 'formatting';
+} );


Instead of a capability check you use to build conditionals, we wrap the conditional logic and accept a list of candidate categories?

function getCategoryWithFallbacks( ...requestedCategories: string[]): string { const knownCategories: Array< { slug: string } > = getCategories(); for ( const requestedCategory of requestedCategories) { if ( knownCategories.some( ( { slug } ) => slug === requestedCategory ) ) { return requestedCategory; } } // Should we throw an error here? 🤔 throw new Error('Terrible choice of category 🤦‍♀️'); } // Usage: registerBlockType( 'my-block/name', { category: getCategoryWithFallbacks( 'layout', 'widgets' ) } );

That's a nice idea! Avoiding having to write a ternary expression would be nice, indeed. Just wondering how we could make this function re-usable across all packages that register blocks. We'll probably need to duplicate it for now?

Yep, we'll need to write it once for each package (FSE, Jetpack…).

Btw, I really like this approach as it's basically future proof. If we change categories again, then it's just a matter of passing it as the last one in the argument.

I'm wondering if it makes sense to move this function over to @wordpress/blocks... 🤔 this way, we'd avoid the current repetition we have across different block repos.

I like that idea. :-)

I'm wondering if it makes sense to move this function over to @wordpress/blocks... 🤔 this way, we'd avoid the current repetition we have across different block repos.

IIUC, if we need this to handle new categories on sites where Gutenberg has not been updated yet (as it handles the other way round automagically), we can't actually move it to a Gutenberg package, because on those sites that utility won't be available. AFAIR, Jetpack imports use packages that are currently available with the installed version of the Gutenberg plugin, not those that are defined in package.json (i.e. @worpdress/blocks). Pinging @jeherve here for help 🙏

If the above is true and we end up dropping the Gutenberg PR, how about we make it into a Calypso package instead?

IIUC, if we need this to handle new categories on sites where Gutenberg has not been updated yet (as it handles the other way round automagically), we can't actually move it to a Gutenberg package, because on those sites that utility won't be available

But isn't the @wordpress/blocks a package that can be installed separately (even though it lives within the Gutenberg repo)? Right now, we need this function in the following packages:

https://github.com/Automattic/wpcom-blocks/pull/178

Update blocks categories jetpack#16363

FSE: Update blocks categories #43670

Update blocks categories block-experiments#110

Wouldn't it just be a matter of publishing a new version of @wordpress/blocks and then updating it on these packages?

I'm fine abandoning that PR and moving it to a Calypso package if we find it's the best way to go, by the way :)

Ah, sorry I read too fast, you actually mention here:

AFAIR, Jetpack imports use packages that are currently available with the installed version of the Gutenberg plugin, not those that are defined in package.json (i.e. @worpdress/blocks). Pinging @jeherve here for help

Let's wait for @jeherve's insights about that, then :)

Thanks!

Have we considered also adding a linting rule that checks the category in warning about new categories as well? Something like checking the category of the registerBlockType() and warning if we know it's a category that's not going to work with older gutenbergs?

sirreal

Looking good, I left a few comments.

This commit has been added but probably will not be included as part of the PR. It's not related to the changeset but was required for me to get my wp-calypso env running.

It looks like there are a few changes to the setup here, it may make sense to break those out into an independent PR. There are multiple concerns here, but the changes are small enough that it's reviewable. At your discretion either way 👍

Should we write tests to check that each block is assigned to the right category names depending on the set of categories? Not sure what is the testing policy for Calypso and what coverage we aim for.

Let's stay focused on testing just the added utility function you added. If we start testing the block registration, we quickly get outside of unit tests.

e2e test may make sense at some point to ensure blocks are in the expected categories, but that's not the scope we're looking at here.

apps/full-site-editing/full-site-editing-plugin/block-helpers/block-helpers.test.ts

apps/full-site-editing/full-site-editing-plugin/block-helpers/block-helpers.ts

apps/full-site-editing/bin/babel-transform.js

apps/full-site-editing/full-site-editing-plugin/newspack-blocks/blog-posts-block-editor.js

fullofcaffeine · 2020-07-01T00:50:43Z

I decided to revert my changes to the premium block categories because:

I wasn't able to test them, they seem to be overridden somewhere. I'm still researching about this but it seems it has to do with https://github.com/Automattic/wp-calypso/tree/master/apps/full-site-editing/full-site-editing-plugin/block-inserter-modifications (see: p1593555242136300-slack-cylon)
Even if I figure out how to change them, there's an open issue here and the team seems to want to keep it in the "New" category for now and create an "Earn" collection for it. It seems there's not an agreement yet though and from what I see, it's out of the scope of this PR.

simison · 2020-07-01T07:33:26Z

Yeah, I'd also just rely on stakeholder team(s) on those blocks and leave them be if they so wish. FYI @lessbloat. 👋

We can consider this unblocked and proceed with the rest of the blocks then? :-)

fullofcaffeine · 2020-07-02T02:06:10Z

Hi Mikael 👋

We can consider this unblocked and proceed with the rest of the blocks then? :-)

I changed all the blocks under FSE I could find (the ones that use registerBlockType). Did I miss any?

The PR for Jetpack is here: Automattic/jetpack#16363.

These are the two outstanding group of blocks that need to be dealt with according to the original issue. Apart from Jetpack and FSE (and Coblocks), what other apps/libs/packages have blocks that need renaming?

sirreal · 2020-07-10T08:23:22Z

Thanks everyone for helping out!

premium-content/buttons - design
premium-content/container - common
premium-content/logged-out-view - common
premium-content/login-button - design
premium-content/subscriber-view - common
a8c/donations - widgets

Premium content is pretty specialized but it also involves site layout, so maybe we can map "common" -> "design" here.
I think a8c/donations is a good fit for widget.

common is one of the legacy categories that needs to be replaced with a new category.

For the remaining common blocks, I'd propose design for all three. These have to do with showing a paywall or paid content, is that correct? That sounds like design more than anything else for me.

premium-content/container - design
premium-content/logged-out-view - design
premium-content/subscriber-view - design

For reference, the valid categories are:

[
	{ slug: 'text', title: __( 'Text' ) },
	{ slug: 'media', title: __( 'Media' ) },
	{ slug: 'design', title: __( 'Design' ) },
	{ slug: 'widgets', title: __( 'Widgets' ) },
	{ slug: 'embed', title: __( 'Embeds' ) },
]

fullofcaffeine · 2020-07-10T15:17:05Z

Thanks everyone for helping out!

premium-content/buttons - design
premium-content/container - common
premium-content/logged-out-view - common
premium-content/login-button - design
premium-content/subscriber-view - common
a8c/donations - widgets
Premium content is pretty specialized but it also involves site layout, so maybe we can map "common" -> "design" here.
I think a8c/donations is a good fit for widget.

common is one of the legacy categories that needs to be replaced with a new category.

For the remaining common blocks, I'd propose design for all three. These have to do with showing a paywall or paid content, is that correct? That sounds like design more than anything else for me.
* `premium-content/container` - `design`

* `premium-content/logged-out-view` - `design`

* `premium-content/subscriber-view` - `design`
For reference, the valid categories are:
[
	{ slug: 'text', title: __( 'Text' ) },
	{ slug: 'media', title: __( 'Media' ) },
	{ slug: 'design', title: __( 'Design' ) },
	{ slug: 'widgets', title: __( 'Widgets' ) },
	{ slug: 'embed', title: __( 'Embeds' ) },
]

They are already mapped to these categories:

Change premium-content/button from layout -> design
Change premium-content/login-button from layout -> design
Change premium-content/container from common -> design
Change premium-content/logged-out-view from common -> design
Change premium-content/subscriber-view from common -> design

sirreal · 2020-07-13T15:37:48Z

Summary of block changes mostly for myself 🙂

Block	Previous	New	Observations
`a8c/donations`	~~`common`~~	`widgets`	Replace legacy category as well (widgets already existed.
`a8c/navigation-menu`	`layout`	`design`
`a8c/post-content`	`layout`	`design`
`a8c/site-credit`	`layout`	`design`
`a8c/site-description`	`layout`	`design`
`a8c/site-title`	`layout`	`design`
`a8c/template`	`layout`	`design`
`a8c/blog-posts`	~~`layout`~~	`widgets`	Replace legacy category as well (widgets already existed.
`a8c/posts-carousel`	~~`layout`~~	`widgets`	Replace legacy category as well (widgets already existed.
`premium-content/buttons`	`design`	`design`	Add fallback `layout` category (this was broken with Gutenberg < 8.4.0?)
`premium-content/container`	`common`	`design`
`premium-content/logged-out-view`	`common`	`design`
`premium-content/login-button`	`design`	`design`	Add fallback `layout` category (this was broken with Gutenberg < 8.4.0?)
`premium-content/subscriber-view`	`common`	`design`

sirreal

A few small changes, I'll go ahead and apply these…

apps/full-site-editing/full-site-editing-plugin/block-helpers/index.ts

apps/full-site-editing/package.json

sirreal · 2020-07-13T16:08:21Z

I applied a few changes to align dependency versions across the monorepo. I also rebased.

apps/full-site-editing/package.json

apps/full-site-editing/tsconfig.json

sirreal · 2020-07-13T19:22:20Z

@noahtallen It looks like this is getting a false negative on the phpcs action

It's trying to run phpcs on a file that was added and deleted in this PR, which errors:

ERROR: The file "apps/full-site-editing/full-site-editing-plugin/block-helpers/block-helpers.ts" does not exist.

sirreal

Tested on Atomic. I see the blog posts and post carousel blocks in the updated categories. I think this is good to go 👍

I'd like to get #43670 (comment) sorted out, but I think that's a false negative and unlikely to affect this after merge.

apps/full-site-editing/tsconfig.json

noahtallen · 2020-07-13T19:41:29Z

@sirreal I think this makes sense. The issue is that we run phpcs on all "changed" files, which includes deleted files. Will have to adjust that logic to only handle added or changed files

noahtallen · 2020-07-13T19:47:21Z

This diff should do it (feel free to commit to this PR to test it)

diff --git a/.github/workflows/full-site-editing-plugin.yml b/.github/workflows/full-site-editing-plugin.yml
index c49652d16a..c794789311 100644
--- a/.github/workflows/full-site-editing-plugin.yml
+++ b/.github/workflows/full-site-editing-plugin.yml
@@ -133,11 +133,8 @@ jobs:
       with:
         token: ${{ secrets.GITHUB_TOKEN }}
 
-    - name: Displaying changed files
-      run: echo ${{ join( fromJson( steps.changes.outputs.all ) ) }}
-
     - name: Execute phpcs on changed files
-      run: ./vendor/bin/phpcs --standard=apps/phpcs.xml ${{ join( fromJson( steps.changes.outputs.all ), ' ' ) }}
+      run: ./vendor/bin/phpcs --standard=apps/phpcs.xml ${{ join( fromJson( steps.changes.outputs.modified ), ' ' ) }} ${{ join( fromJson( steps.changes.outputs.added ), ' ' ) }}
       if: ${{ steps.changes.outputs.all != '' }}
     
     - name: No changes found
ddd

fullofcaffeine · 2020-07-14T02:32:06Z

Tested on Atomic. I see the blog posts and post carousel blocks in the updated categories. I think this is good to go +1

I'd like to get #43670 (comment) sorted out, but I think that's a false negative and unlikely to affect this after merge.

@Automattic/good-mountain Fellows, I ended up getting into a 🐇 🕳️ and couldn't deploy today. But it was for a good cause (hopefully!). It's related to the previous report I made here. More details below.

It seems some earn (premium) blocks were broken for a while.While testing on Atomic sites, we've found the following:

In master's FSE, when using older versions of Gutenberg, the premium-content/login-button and premium-content/buttons were not appearing in the picker's (because design category is not available there). The premium-content/content can be found and added, but one of its sub-blocks appears erro'ed.
In master's FSE, when using a recent (> 8.3.0) version of Gutenberg, the blocks are shown correctly in the picker but 1) premium-content/buttons fails upon being added to the page 2) premium-content/login-button works 3) premium-content/content can be found and inserted, but one of its sub-blocks renders an error message.

The difference when testing with this branch's FSE is that in older Gutenberg versions where the design category is not available, the blocks are registered correctly in the legacy category provided so that they are found in the picker. But they err when added to the page. When using more recent versions of Gutenberg, the same behavior I described in point 2 above happens.

It seems these issues are independent of the changes added here. Still, the changes here make the two "problematic" premium blocks appear on Gutenberg versions < 8.3.0. After discussing this with @gwwar and @deBhal, I decided to postpone the deploy for now. More details here: p1594677291077000-slack-create-gardeners.

@deBhal is gardening, and this bug probably falls on gardeners' plate. We spent some time pairing on this today, and he's still looking into it as I end my day now. 🇦🇺

I could have managed to deploy this today, but I wanted to wait to understand what it's about and if we need to do anything in the category side. I'm pretty sure that this can be merged and perhaps deployed tomorrow.

*With the help of @deBhal, who kindly offered to help me deploy this PR and paired with me on this issue, thanks a lot!

sirreal · 2020-07-14T08:02:50Z

Conversation on handling broken blocks: pbAok1-1ez-p2

gwwar

Thanks for shepherding the update @fullofcaffeine! This tests well for Premium Content blocks on Simple Sites (edge and 8.3).

@Automattic/serenity is looking into potential breakages into Atomic from Premium Content, but it shouldn't affect this PR. We'll follow up shortly.

Context: #43198. - Also add a helper function for FSE blocks that can be used to check if old category names exist in the store and fall-backs to an older version(s) otherwise. This function should be used when the updated category is a completely new category being introduced by a new version of Gutenberg. You then pass this new category + the older categorie(s) that will be tried in sequence if the previous one was not found. - Tweaked the FSE Jest configuration to support TypeScript.

…ontent The fallback was causing these blocks to appear in older versions of Gutenberg where the `design` category was not available. Until here, all good. However, they were all er'ing upon insertion. We thought it would be better to rollback this change for now.

a8ci18n reviewed Jun 25, 2020

View reviewed changes

fullofcaffeine changed the title ~~FSE: Update/fse blocks categories collections~~ FSE: Update blocks categories Jun 25, 2020

sirreal reviewed Jun 25, 2020

View reviewed changes

sirreal assigned fullofcaffeine Jun 25, 2020

sirreal added [Goal] Gutenberg Working towards full integration with Gutenberg [Status] In Progress labels Jun 25, 2020

sirreal reviewed Jun 26, 2020

View reviewed changes

apps/full-site-editing/full-site-editing-plugin/block-helpers/block-helpers.test.ts Outdated Show resolved Hide resolved

apps/full-site-editing/full-site-editing-plugin/block-helpers/block-helpers.ts Outdated Show resolved Hide resolved

fullofcaffeine force-pushed the update/fse-blocks-categories-collections branch from 8308272 to f686f8c Compare June 26, 2020 23:16

fullofcaffeine commented Jun 26, 2020

View reviewed changes

apps/full-site-editing/bin/babel-transform.js Show resolved Hide resolved

fullofcaffeine force-pushed the update/fse-blocks-categories-collections branch 2 times, most recently from a5d4c76 to a9f82b2 Compare June 27, 2020 00:57

fullofcaffeine marked this pull request as ready for review June 29, 2020 21:37

fullofcaffeine requested review from a team as code owners June 29, 2020 21:37

simison mentioned this pull request Jun 29, 2020

Updated default block categories for Automattic blocks #43198

Closed

6 tasks

sirreal reviewed Jun 30, 2020

View reviewed changes

apps/full-site-editing/full-site-editing-plugin/newspack-blocks/blog-posts-block-editor.js Outdated Show resolved Hide resolved

fullofcaffeine force-pushed the update/fse-blocks-categories-collections branch from c9a4df3 to 8ba7810 Compare July 1, 2020 00:50

simison added the [Status] Needs Rebase label Jul 1, 2020

fullofcaffeine force-pushed the update/fse-blocks-categories-collections branch 2 times, most recently from 94a1eea to 3089e0c Compare July 2, 2020 01:59

fullofcaffeine removed the [Status] Needs Rebase label Jul 2, 2020

fullofcaffeine mentioned this pull request Jul 2, 2020

Update blocks categories Automattic/jetpack#16363

Merged

35 tasks

fullofcaffeine force-pushed the update/fse-blocks-categories-collections branch 2 times, most recently from 3ec65b0 to f2bf6c0 Compare July 3, 2020 02:01

sirreal reviewed Jul 13, 2020

View reviewed changes

sirreal force-pushed the update/fse-blocks-categories-collections branch from 301b4c8 to c778506 Compare July 13, 2020 15:55

fullofcaffeine commented Jul 13, 2020

View reviewed changes

apps/full-site-editing/package.json Show resolved Hide resolved

sirreal reviewed Jul 13, 2020

View reviewed changes

apps/full-site-editing/tsconfig.json Outdated Show resolved Hide resolved

apps/full-site-editing/tsconfig.json Outdated Show resolved Hide resolved

fullofcaffeine force-pushed the update/fse-blocks-categories-collections branch from 7077925 to e043acf Compare July 13, 2020 18:09

sirreal approved these changes Jul 13, 2020

View reviewed changes

sirreal reviewed Jul 13, 2020

View reviewed changes

apps/full-site-editing/tsconfig.json Outdated Show resolved Hide resolved

fullofcaffeine force-pushed the update/fse-blocks-categories-collections branch from 5bd5e9e to 15992ef Compare July 13, 2020 21:22

deBhal mentioned this pull request Jul 13, 2020

Update FSE plugin to version to 1.13 #44125

Merged

31 tasks

fullofcaffeine force-pushed the update/fse-blocks-categories-collections branch from 15992ef to 6b2e38a Compare July 14, 2020 01:48

gwwar added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. and removed [Status] In Progress labels Jul 14, 2020

gwwar approved these changes Jul 14, 2020

View reviewed changes

fullofcaffeine added 3 commits July 14, 2020 19:06

Fix workflow logic to not run phpcs for deleted files

fed1eeb

fullofcaffeine force-pushed the update/fse-blocks-categories-collections branch from 0bd07b6 to 4e0ec42 Compare July 15, 2020 00:14

fullofcaffeine merged commit 65fe392 into master Jul 15, 2020

fullofcaffeine deleted the update/fse-blocks-categories-collections branch July 15, 2020 01:05

matticbot removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Jul 15, 2020

fullofcaffeine mentioned this pull request Apr 20, 2022

[ETK] Chore: Remove unused block-helpers module #62932

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

FSE: Update blocks categories #43670

FSE: Update blocks categories #43670

fullofcaffeine commented Jun 25, 2020 •

edited

Loading

matticbot commented Jun 25, 2020

matticbot commented Jun 25, 2020

a8ci18n Jun 25, 2020

matticbot commented Jun 25, 2020

sirreal left a comment

sirreal Jun 25, 2020

fullofcaffeine Jun 25, 2020

sirreal Jun 25, 2020

fullofcaffeine Jun 25, 2020

fullofcaffeine Jul 3, 2020

simison Jul 3, 2020

WunderBart Jul 6, 2020

fullofcaffeine Jul 6, 2020 •

edited

Loading

fullofcaffeine Jul 6, 2020

deBhal Jul 15, 2020 •

edited

Loading

sirreal left a comment

fullofcaffeine commented Jul 1, 2020 •

edited

Loading

simison commented Jul 1, 2020

fullofcaffeine commented Jul 2, 2020 •

edited

Loading

sirreal commented Jul 10, 2020

fullofcaffeine commented Jul 10, 2020

sirreal commented Jul 13, 2020

sirreal left a comment

sirreal commented Jul 13, 2020

sirreal commented Jul 13, 2020

sirreal left a comment

noahtallen commented Jul 13, 2020

noahtallen commented Jul 13, 2020 •

edited

Loading

fullofcaffeine commented Jul 14, 2020 •

edited

Loading

sirreal commented Jul 14, 2020

gwwar left a comment

FSE: Update blocks categories #43670

FSE: Update blocks categories #43670

Conversation

fullofcaffeine commented Jun 25, 2020 • edited Loading

Changes proposed in this Pull Request

Related PRs

Categories

TODO

Outstanding questions

Testing instructions

Atomated tests

To manually test the changes

Test the scenarios above in the following environments:**

matticbot commented Jun 25, 2020

matticbot commented Jun 25, 2020

Choose a reason for hiding this comment

matticbot commented Jun 25, 2020

sirreal 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

fullofcaffeine Jul 6, 2020 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

deBhal Jul 15, 2020 • edited Loading

Choose a reason for hiding this comment

sirreal left a comment

Choose a reason for hiding this comment

fullofcaffeine commented Jul 1, 2020 • edited Loading

simison commented Jul 1, 2020

fullofcaffeine commented Jul 2, 2020 • edited Loading

sirreal commented Jul 10, 2020

fullofcaffeine commented Jul 10, 2020

sirreal commented Jul 13, 2020

sirreal left a comment

Choose a reason for hiding this comment

sirreal commented Jul 13, 2020

sirreal commented Jul 13, 2020

sirreal left a comment

Choose a reason for hiding this comment

noahtallen commented Jul 13, 2020

noahtallen commented Jul 13, 2020 • edited Loading

fullofcaffeine commented Jul 14, 2020 • edited Loading

sirreal commented Jul 14, 2020

gwwar left a comment

Choose a reason for hiding this comment

fullofcaffeine commented Jun 25, 2020 •

edited

Loading

fullofcaffeine Jul 6, 2020 •

edited

Loading

deBhal Jul 15, 2020 •

edited

Loading

fullofcaffeine commented Jul 1, 2020 •

edited

Loading

fullofcaffeine commented Jul 2, 2020 •

edited

Loading

noahtallen commented Jul 13, 2020 •

edited

Loading

fullofcaffeine commented Jul 14, 2020 •

edited

Loading