Storage Add Ons: Implement dropdown checkout functionality #81340

jeyip · 2023-09-04T03:16:06Z

Related to #79041 (comment)
Issue https://github.com/Automattic/martech/issues/2025
Tracking https://github.com/Automattic/martech/issues/2023

Proposed Changes

Update checkout cart for /start signup onboarding flow with storage add ons

GIFs

To be left as a Follow Up for the Future

Make the storage add-on in checkout cart a dropdown ( to allow user to switch between storage add-ons ) @saygunnyc has stated that this is something we can build on iteratively

Testing Instructions

Smoke test flows: in PCYsg-RDT-p2 and ensure that a free plan ( if available ) and a paid plan can be purchased
- /setup/newsletter ( Stepper flows should be unaffected by our changes )
  - navigate to http://calypso.localhost:3000/setup/newsletter as a logged in user
  - Complete onboarding steps until you’ve reached the plans page
- /start/domains
  - Navigate to http://calypso.localhost:3000/start/domains
  - Select a custom domain like .org, .blog, etc.
  - Navigate to the plans page
- /start/hosting
  - Navigate to http://calypso.localhost:3000/start/hosting
  - Navigate to the plans page
- /start/import
  - Navigate to http://calypso.localhost:3000/start/import
  - Select any domain, free or custom
  - Navigate to the plans page
- /start/onboarding-pm
  - Navigate to http://calypso.localhost:3000/start/onboarding-pm
  - Select any domain, free or custom
  - Navigate to the plans page
- /start/onboarding-with-email
  - Navigate to http://calypso.localhost:3000/start/onboarding-with-email
  - Select any domain, free or custom
  - Select the provided email option
  - Navigate to the plans page
- /start/with-themes
  - Go to https://wordpress.com/themes while logged out and pick a Premium theme.
  - Alternatively, copy the URL of the “Pick this design” button and paste it in a logged-in browser session (it should be something like wordpress.com/start/with-theme?theme=yuga&premium=true&theme_type=premium)
  - Proceed with the onboarding until you get to the “Choose a plan” step
- /start/personal
  - Navigate to http://calypso.localhost:3000/start/personal
  - Select any domain, free or custom
- /start/personal-monthly
  - Navigate to http://calypso.localhost:3000/start/personal
  - Select any domain, free or custom
- /start/personal-2y
  - Navigate to http://calypso.localhost:3000/start/personal
  - Select any domain, free or custom
- /start/business
  - Navigate to http://calypso.localhost:3000/start/business
  - Select any domain, free or custom
- /setup/wooexpress ( since wooexpress has no onboarding plans page, it should be unaffected by our changes )
  - Navigate to http://calypso.localhost:3000/setup/wooexpress ( If testing in a dev environment, make sure to navigate to the wordpress.com URL above to create the initial site. Then switch over to a dev URL. For some reason, using a dev URL to initially set up wooexpress doesn’t work as expected )
  - Wait until redirected to the wp-admin page for the newly created atomic site
  - From the wp-admin page click, on Upgrades > Plans
  - Alternatively, navigate to http://calypso.localhost:3000/plans/{SITE_SLUG}

Pre-merge Checklist

Has the general commit checklist been followed? (PCYsg-hS-p2)
https://wpcalypso.wordpress.com/devdocs/docs/testing/index.md for your changes?
Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
Have you checked for TypeScript, React or other console errors?
Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?

github-actions · 2023-09-04T03:16:22Z

Calypso Live (direct link)

	https://calypso.live?image=registry.a8c.com/calypso/app:build-81814

Jetpack Cloud live (direct link)

	https://calypso.live?image=registry.a8c.com/calypso/app:build-81814&env=jetpack

matticbot · 2023-09-04T03:28:39Z

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~598 bytes added 📈 [gzipped])

name                               parsed_size           gzip_size
update-design-flow                      +610 B  (+0.0%)     +185 B  (+0.1%)
link-in-bio-tld-flow                    +608 B  (+0.0%)     +175 B  (+0.0%)
plans                                   +532 B  (+0.0%)     +136 B  (+0.0%)
plugins                                 +495 B  (+0.0%)     +132 B  (+0.0%)
signup                                  +463 B  (+0.1%)     +142 B  (+0.2%)
home                                    +229 B  (+0.0%)      +71 B  (+0.0%)
free-flow                               +229 B  (+0.0%)      +72 B  (+0.0%)
jetpack-connect                         +228 B  (+0.0%)      +75 B  (+0.0%)
accept-invite                           +228 B  (+0.1%)      +72 B  (+0.1%)
write-flow                              +227 B  (+0.0%)      +72 B  (+0.0%)
videopress-flow                         +227 B  (+0.0%)      +74 B  (+0.0%)
build-flow                              +227 B  (+0.0%)      +72 B  (+0.0%)
checkout                                +166 B  (+0.0%)      +38 B  (+0.0%)
domains                                 +164 B  (+0.0%)      +36 B  (+0.0%)
tailored-ecommerce-flow                 +162 B  (+0.0%)      +37 B  (+0.0%)
sensei-flow                             +162 B  (+0.0%)      +37 B  (+0.0%)
podcasts-flow                           +162 B  (+0.0%)      +37 B  (+0.0%)
copy-site-flow                          +162 B  (+0.0%)      +37 B  (+0.0%)
themes                                  +149 B  (+0.0%)      +39 B  (+0.0%)
theme                                   +149 B  (+0.0%)      +39 B  (+0.0%)
site-purchases                          +147 B  (+0.0%)      +34 B  (+0.0%)
site-blocks                             +147 B  (+0.0%)      +37 B  (+0.0%)
security                                +147 B  (+0.0%)      +37 B  (+0.0%)
purchases                               +147 B  (+0.0%)      +34 B  (+0.0%)
privacy                                 +147 B  (+0.0%)      +37 B  (+0.0%)
notification-settings                   +147 B  (+0.0%)      +37 B  (+0.0%)
me                                      +147 B  (+0.0%)      +37 B  (+0.0%)
marketplace                             +147 B  (+0.0%)      +32 B  (+0.0%)
link-in-bio-flow-domain                 +147 B  (+0.6%)      +37 B  (+0.6%)
jetpack-cloud-pricing                   +147 B  (+0.0%)      +37 B  (+0.0%)
jetpack-cloud-features-comparison       +147 B  (+0.0%)      +37 B  (+0.0%)
help                                    +147 B  (+0.0%)      +37 B  (+0.0%)
email                                   +147 B  (+0.0%)      +37 B  (+0.0%)
connect-domain                          +147 B  (+0.6%)      +37 B  (+0.6%)
account-close                           +147 B  (+0.0%)      +37 B  (+0.0%)
account                                 +147 B  (+0.0%)      +39 B  (+0.0%)
add-ons                                  +31 B  (+0.0%)       +7 B  (+0.0%)
gutenberg-editor                         +15 B  (+0.0%)       +0 B

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Async-loaded Components (~148 bytes added 📈 [gzipped])

name                                                              parsed_size           gzip_size
async-load-signup-steps-plans-theme-preselected                        +349 B  (+0.1%)     +102 B  (+0.1%)
async-load-signup-steps-plans                                          +349 B  (+0.1%)     +102 B  (+0.1%)
async-load-calypso-my-sites-checkout-modal                             +166 B  (+0.0%)      +41 B  (+0.0%)
async-load-calypso-blocks-editor-checkout-modal                        +151 B  (+0.0%)      +41 B  (+0.0%)
async-load-calypso-my-sites-current-site-stale-cart-items-notice       +147 B  (+0.7%)      +37 B  (+0.7%)
async-load-signup-steps-add-ons                                         +32 B  (+0.0%)       +9 B  (+0.0%)
async-load-calypso-blocks-app-banner                                    +15 B  (+0.0%)       +0 B

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

jeyip · 2023-09-04T19:17:52Z

client/lib/signup/step-actions/index.js

@@ -1270,7 +1269,7 @@ export function isNewOrExistingSiteFulfilled( stepName, defaultDependencies, nex
 	}
 }

-export const buildUpgradeFunction = ( planProps, cartItem ) => {
+export const buildUpgradeFunction = ( planProps, cartItem, addOnItem ) => {


Note:

Amendments to this file allow us to add storage add-ons to the shopping cart in signup onboarding flows

jeyip · 2023-09-05T04:50:33Z

Note:

There's a delay between when a storage upgrade add-on is purchased and when the purchase is reflected in the /plans page ( it will look as if nothing has changed until a minute or two later ). I'll work more on this tomorrow

southp

@jeyip I didn't manage to look into the code deeply today, but the /start flow works as expected :)

Since we are now restricting it into /start only, could you help remove all the unncessary part outside of that? That will greatly reduce the required amout of code review and testing :)

southp · 2023-09-06T10:46:47Z

client/my-sites/add-ons/hooks/use-add-ons.ts

@@ -140,7 +140,7 @@ const useAddOns = ( siteId?: number ): ( AddOnMeta | null )[] => {

 		const spaceUpgradesPurchased: number[] = [];

-		if ( filteredTransactions?.length ) {
+		if ( filteredTransactions?.length && siteId ) {


I'm not sure I understand why the siteId all of a sudden is needed here. Could you help me understand?

Thanks for the patience!

This was meant to fix a bug when we call use-add-ons in the context of onboarding. For some reason, add-on data incorrectly decides that both 50GB add-ons and 100GB add-ons are already purchased, even though no site has been created yet.

To elaborate on why, filteredTransactions returns transactions for a given site when siteId exists. When, however, siteId is undefined, filteredTransactions fetches all transactions for a user, regardless of what site the purchase was made on.

Since I had made some space upgrade add-on purchase in the past on any site, the logic then proceeded to mark add-on data as purchased

wp-calypso/client/my-sites/add-ons/hooks/use-add-ons.ts

Lines 231 to 244 in 426d78e

// if storage add on is already purchased

if (

spaceUpgradesPurchased.findIndex(

( spaceUpgrade ) => spaceUpgrade === addOn.quantity

) >= 0 &&

product

) {

return {

...addOn,

name,

description,

purchased: true,

};

}

By checking for a truthy siteId, I intended to only look for space upgrade add-on transactions if the site has already been created ( and we're in the plans page )

With that being said, I wrote this when I was really tired 😴 , so we might consider better inline documentation or exploring alternative ways to address the bug. Ex. It looked like it might be possible to update the params for filterTransactions such that, when called with an undefined siteId, it returns no transactions, rather than all transactions, but I haven't looked to closely yet

Thanks for the explanation. It looks like the transaction data is used for filtering out the storage add-ons that have lower volumn than the owned one. Also, how the whole transaction data is fetched and filtered is actually quite non-ideal –– it fetches the whole transaction history and than filter from the client side, while all these should be done from the server side so our users don't have to waste their bandwidth and local computational resources to perform all these. Since correcting the whole thing would be out of scope, let's start by not fetching those transaction data in the onboarding flow since that doesn't make sense. It'd involve some level of decoupling, but we will have a cleaner code without tricky conditions needing explicit documentation :)

I took a very simplistic approach to this in ce39121 and 21e2cfb. I added a guard with isInSignup to prevent fetching. I'm not sure if that's the best flag, but it seemed reasonable to me

jeyip · 2023-09-06T22:39:58Z

I didn't manage to look into the code deeply today, but the /start flow works as expected :)

Since we are now restricting it into /start only, could you help remove all the unncessary part outside of that? That will greatly reduce the required amout of code review and testing :)

Working on it now :D

client/signup/config/steps-pure.js

jeyip · 2023-09-07T04:40:44Z

@vinimotaa 👋

Hey Vini! After purchasing the space storage add-on, it takes a minute or two for all of the information to be correctly updated in the database

When a user visits the plans page while the data is still being updated, they'll see incorrect storage information. Do you have thoughts on what we should display for the storage label to indicate the pending state?

One thing to note is that it's a bit of an edge case ( the user has to visit the plans page within a few minutes after making their purchase

I was also curious if we could figure out how to handle larger cost strings in the storage add on dropdown. My first thought is to round the cost up or down to the nearest dollar, or to hide the cost after selection

southp · 2023-09-07T13:07:07Z

@jeyip Sorry for being ignorant about the design decisions made in the past, but could you help me point out the reference of showing the standard storage + the add-on storage in the plans grid? I'm asking since I feel this is a bit confusing:

If we want to show the accumulated space, then I'm wondering if we should also do that for Free / Personal / Premium. Nothing prevent them from purchasing storage add-ons anyway :)
Overall I feel it's risky to show the accumulated space without further explanation. As someone who is familar with that label, I might think the eCommerce plan has 100G space so I'd have 100G + 50G space once upgraded. Have we considered to separate them as two labels or something if we really want to emphasize the extra space from the owning storage add-on in the plans grid?

Also cc @gmovr and @dzver here in case you both happen to know this on top of your mind :)

dzver · 2023-09-07T14:46:47Z

@southp I don't know on top of my head. My goal is to unblock this task so that it gets shipped, and I'm leaning toward simplification rather than making things more complex. Whatever the design is, it has to show we support space upgrades, and that's pretty much the only solid requirement.

@jeyip could you point to the latest design on this? I don't see a link in the PR or the corresponding issue.

jeyip · 2023-09-07T18:02:05Z

Sorry for being ignorant about the design decisions made in the past, but could you help me point out the reference of showing the standard storage + the add-on storage in the plans grid?

Sure I'd be happy to:

p9Jlb4-7Ui-p2
https://github.com/Automattic/martech/issues/1907

'm wondering if we should also do that for Free / Personal / Premium. Nothing prevent them from purchasing storage add-ons anyway :)

"As the 50 GB and 100GB storage upgrades don't make sense for Free, Personal, and Premium –Simply upgrading to the Business plan would provide 50 GB space much cheaper. I didn't include storage options for those plans on the grid even though they are technically possible."

https://github.com/Automattic/martech/issues/1907#issuecomment-1630537955

southp · 2023-09-08T03:43:05Z

Thanks for pointing out the references for me, @jeyip :)

From my view, this design decision works with the dropdowns, since the label and the dropdowns are obviously communicating different things. However, when all that we have is the label, it doesn't work since they look the same but having different meanings. If we still agree to the original decision of rolling the add-on UI out to /start only, I think it's the best to not touch the label and just leave /plans the way it is –– we already have the storage add-ons and it's been this way, so it shouldn't be a deal breaker. We will then work on /plans as the next milestone.

Does that make sense to you?

jeyip · 2023-09-12T23:05:15Z

If we still agree to the original decision of rolling the add-on UI out to /start only, I think it's the best to not touch the label and just leave /plans the way it is –– we already have the storage add-ons and it's been this way, so it shouldn't be a deal breaker. We will then work on /plans as the next milestone.

Does that make sense to you?

This does 🙂 If we end up changing our minds, we can draft a relatively quick PR to update the storage add-ons label in /plans as well

chriskmnds · 2023-09-22T10:22:53Z

client/my-sites/plan-features-2023-grid/index.tsx

@@ -100,6 +102,7 @@ export interface PlanFeatures2023GridProps {
 	planTypeSelectorProps: PlanTypeSelectorProps;
 	// temporary: callback ref to scroll Odie AI Assistant into view once "Compare plans" button is clicked
 	observableForOdieRef: ( observableElement: Element | null ) => void;
+	selectedStorageOptions?: SelectedStorageOptionForPlans;


selectedStorageOptions prop doesn't seem relevant here and should be removed.
The only relevant type for your case is PlanFeatures2023GridType below I think

(it's a little confusing, I know. parts that are being cleaned up in other work)

Thanks for pointing this out! I removed the unnecessary type here d5a8c5c

chriskmnds · 2023-09-22T10:25:40Z

client/my-sites/plan-features-2023-grid/index.tsx

@@ -111,6 +114,7 @@ interface PlanFeatures2023GridType extends PlanFeatures2023GridProps {
 	isPlanUpgradeCreditEligible: boolean;
 	// temporary: element ref to scroll comparison grid into view once "Compare plans" button is clicked
 	plansComparisonGridRef: ForwardedRef< HTMLDivElement >;
+	selectedStorageOptions?: SelectedStorageOptionForPlans;


so this is fine and the only place you need to define this

jeyip · 2023-09-22T23:13:24Z

The final bit we need to address is the regression of the /start/domain flow.

There was a cartItem dependency for the site-picker step in the domain flow that needed to be updated to cartItems. On closer inspection, however, it appears as if the site-picker step doesn't need the dependency at all. The logic within the site-picker component makes no indication of needing it, so I remove the cartItem dependency instead. Some smoke testing seems to confirm this.

Additionally, the plans step in the domain flow was being skipped under certain circumstances, so we update the provided cartItem dependency to cartItems in those circumstances as well. As far as I can tell, the domain flow is now fixed

As it exists today, storage labels show the default amount of storage in the pricing grid, even if a storage upgrade add-on is purchased. We ensure that we continue to do so if the storage add-on dropdown is not displayed

Revert isEmpty change Remove unnecessary check for cartItem Fix pro plan upgrade button Fix plan step unit test Fix typescript errors

There was a cartItem dependency for the site-picker step that needed to be updated to cartItems. On closer inspection, however, it appears as if the site-picker step doesn't need the dependency at all. The logic within the site-picker component makes no indication of needing it, so I remove the cartItem dependency instead. Additionally, the plans step in the domain flow was being skipped under certain circumstances, so we update the provided cartItem dependency to cartItems in those circumstances as well.

southp

Beautifully done. Thanks for the great effort you've put into the fix, @jeyip . It's impressive to see you go extra miles further tidying the code up while fixing it up.

southp · 2023-09-25T07:00:59Z

Also, since @chriskmnds has two PRs based on this PR(#81960 and #82054), I'm deploying this shortly to move things forward :)

jeyip added the Storage Addon label Sep 4, 2023

jeyip self-assigned this Sep 4, 2023

jeyip changed the base branch from trunk to add/storage-addon-dropdown-UI-functionality September 4, 2023 03:16

jeyip marked this pull request as ready for review September 4, 2023 04:29

jeyip commented Sep 4, 2023

View reviewed changes

jeyip requested review from a team and aneeshd16 September 4, 2023 23:45

matticbot added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels Sep 4, 2023

jeyip force-pushed the add/storage-addon-dropdown-UI-functionality branch from 86e9897 to fe2ed2a Compare September 5, 2023 20:49

jeyip force-pushed the add/storage-addon-dropdown-checkout-functionality branch from ab7ad7b to d4e35ef Compare September 5, 2023 23:31

southp reviewed Sep 6, 2023

View reviewed changes

jeyip force-pushed the add/storage-addon-dropdown-UI-functionality branch from e5a8436 to 4a92911 Compare September 6, 2023 18:09

jeyip force-pushed the add/storage-addon-dropdown-checkout-functionality branch from e7f13f0 to 9527344 Compare September 6, 2023 22:46

jeyip force-pushed the add/storage-addon-dropdown-UI-functionality branch from 3e7843b to 1ad269a Compare September 7, 2023 00:11

jeyip force-pushed the add/storage-addon-dropdown-checkout-functionality branch 2 times, most recently from 9a05d1b to 7130bd4 Compare September 7, 2023 00:21

jeyip commented Sep 7, 2023

View reviewed changes

client/signup/config/steps-pure.js Outdated Show resolved Hide resolved

jeyip force-pushed the add/storage-addon-dropdown-UI-functionality branch from 7f500b3 to 8384f7a Compare September 14, 2023 00:29

chriskmnds reviewed Sep 22, 2023

View reviewed changes

jeyip added 19 commits September 24, 2023 13:59

Add dropdown functionality to storage add-on upsell

2ecdf22

Update plans-ecommerce-fulfilled step

cd3088d

Always show default storage option slug for plan

e924a3e

As it exists today, storage labels show the default amount of storage in the pricing grid, even if a storage upgrade add-on is purchased. We ensure that we continue to do so if the storage add-on dropdown is not displayed

Support multiple checkout cart items in buildUpgradeFunction

43854c3

Fix various bugs and units tests

3ed3ceb

Revert isEmpty change Remove unnecessary check for cartItem Fix pro plan upgrade button Fix plan step unit test Fix typescript errors

Don't fetch add-on transaction history in onboarding

1f52d93

Build cartItems in the plan features grid

df0663e

Fix case for selectedStorageOptionForPlans type

6e60b88

Move add-on transaction filter into block scope

9d6477b

Disable billing transaction query in onboarding

387473c

Fix upgrade click storage add-on data retrieval

d442efd

Add named tuple destructuring for clearer tests

a81d1a2

Update inline comment about check for plan free slug

9e4b4df

DRY getPlanCartItem

e1de765

Handle cartItems in stepper flows

88853b2

Fix stepper onSelectPlan type error

5cb0d90

Remove unnecessary selectedStorageOption type

1fe35c4

Add inline TODO note about deprecation of cartItem

d09c44b

jeyip force-pushed the add/storage-addon-dropdown-checkout-functionality branch from 9da13ef to d09c44b Compare September 24, 2023 20:59

jeyip mentioned this pull request Sep 25, 2023

Storage Add-Ons: Add tracks event #81816

Merged

7 tasks

southp approved these changes Sep 25, 2023

View reviewed changes

southp merged commit 5975148 into trunk Sep 25, 2023

southp deleted the add/storage-addon-dropdown-checkout-functionality branch September 25, 2023 07:01

github-actions bot removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Sep 25, 2023

BogdanUngureanu mentioned this pull request Sep 25, 2023

LoTS: Community themes not getting installed after onboarding #82102

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Storage Add Ons: Implement dropdown checkout functionality #81340

Storage Add Ons: Implement dropdown checkout functionality #81340

jeyip commented Sep 4, 2023 •

edited

Loading

github-actions bot commented Sep 4, 2023 •

edited by matticbot

Loading

matticbot commented Sep 4, 2023 •

edited

Loading

jeyip Sep 4, 2023

jeyip commented Sep 5, 2023

southp left a comment

southp Sep 6, 2023

jeyip Sep 15, 2023 •

edited

Loading

southp Sep 19, 2023

jeyip Sep 20, 2023 •

edited

Loading

jeyip commented Sep 6, 2023

jeyip commented Sep 7, 2023 •

edited

Loading

southp commented Sep 7, 2023

dzver commented Sep 7, 2023

jeyip commented Sep 7, 2023 •

edited

Loading

southp commented Sep 8, 2023

jeyip commented Sep 12, 2023 •

edited

Loading

chriskmnds Sep 22, 2023

jeyip Sep 22, 2023

chriskmnds Sep 22, 2023

jeyip commented Sep 22, 2023 •

edited

Loading

southp left a comment

southp commented Sep 25, 2023

	// if storage add on is already purchased
	if (
	spaceUpgradesPurchased.findIndex(
	( spaceUpgrade ) => spaceUpgrade === addOn.quantity
	) >= 0 &&
	product
	) {
	return {
	...addOn,
	name,
	description,
	purchased: true,
	};
	}

Storage Add Ons: Implement dropdown checkout functionality #81340

Storage Add Ons: Implement dropdown checkout functionality #81340

Conversation

jeyip commented Sep 4, 2023 • edited Loading

Proposed Changes

GIFs

To be left as a Follow Up for the Future

Testing Instructions

Pre-merge Checklist

github-actions bot commented Sep 4, 2023 • edited by matticbot Loading

matticbot commented Sep 4, 2023 • edited Loading

jeyip Sep 4, 2023

Choose a reason for hiding this comment

jeyip commented Sep 5, 2023

southp left a comment

Choose a reason for hiding this comment

southp Sep 6, 2023

Choose a reason for hiding this comment

jeyip Sep 15, 2023 • edited Loading

Choose a reason for hiding this comment

southp Sep 19, 2023

Choose a reason for hiding this comment

jeyip Sep 20, 2023 • edited Loading

Choose a reason for hiding this comment

jeyip commented Sep 6, 2023

jeyip commented Sep 7, 2023 • edited Loading

southp commented Sep 7, 2023

dzver commented Sep 7, 2023

jeyip commented Sep 7, 2023 • edited Loading

southp commented Sep 8, 2023

jeyip commented Sep 12, 2023 • edited Loading

chriskmnds Sep 22, 2023

Choose a reason for hiding this comment

jeyip Sep 22, 2023

Choose a reason for hiding this comment

chriskmnds Sep 22, 2023

Choose a reason for hiding this comment

jeyip commented Sep 22, 2023 • edited Loading

southp left a comment

Choose a reason for hiding this comment

southp commented Sep 25, 2023

jeyip commented Sep 4, 2023 •

edited

Loading

github-actions bot commented Sep 4, 2023 •

edited by matticbot

Loading

matticbot commented Sep 4, 2023 •

edited

Loading

jeyip Sep 15, 2023 •

edited

Loading

jeyip Sep 20, 2023 •

edited

Loading

jeyip commented Sep 7, 2023 •

edited

Loading

jeyip commented Sep 7, 2023 •

edited

Loading

jeyip commented Sep 12, 2023 •

edited

Loading

jeyip commented Sep 22, 2023 •

edited

Loading