feat: add new `mc-scripts config:sync` command #2524

Rhotimee · 2022-03-24T13:58:12Z

Implement a new config:sync command for mc-scripts.

See changelog for more information

changeset-bot · 2022-03-24T13:58:15Z

🦋 Changeset detected

Latest commit: fe05ab7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages

Name	Type
@commercetools-frontend/mc-scripts	Minor
@commercetools-frontend/application-config	Minor
merchant-center-application-template-starter	Patch
playground	Patch
@commercetools-frontend/application-shell	Minor
@commercetools-frontend/cypress	Minor
@commercetools-frontend/mc-html-template	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

vercel · 2022-03-24T13:58:15Z

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/commercetools/merchant-center-application-kit/2AMw91rpjrtHxXfpLSpgUjvLz2DH
✅ Preview: https://merchant-center-application-kit-git-shield-711575-commercetools.vercel.app

emmenko

Thanks, functionality wise looks good. I left some feedback to improve different minor things.

emmenko · 2022-03-25T12:44:38Z

packages/application-config/src/load-config.ts

@@ -62,6 +62,16 @@ const explorer = cosmiconfigSync(moduleName, {
  },
 });

+export const getCustomApplicationConfigPath = () => {


Nit: I think we can simply name this getConfigPath (as we have the other functions loadConfig, processConfig)

emmenko · 2022-03-29T12:34:04Z

.changeset/eleven-nails-change.md

+This command allows users to synchronize the local custom application config with the one available on the merchant center organization.
+
+It creates a new custom application if there is no custom application with the entryPointUriPath in the local config file.
+
+If there is a custom application with the entryPointUriPath available in the merchant center, it is updated with the local configuration upon confirmation.


Suggested change

This command allows users to synchronize the local custom application config with the one available on the merchant center organization.

It creates a new custom application if there is no custom application with the entryPointUriPath in the local config file.

If there is a custom application with the entryPointUriPath available in the merchant center, it is updated with the local configuration upon confirmation.

This command allows users to synchronize the local Custom Application config with the Merchant Center. The sync implies that a new Custom Application will be created or an existing one will be updated.

Developers can use the `config:sync` command to automatically manage the configuration of a Custom Application from the config file instead of having to manually fill out the information in the Merchant Center.

If a new Custom Application needs to be created, an interactive prompt will ask the user to select the Organization where the Custom Application should be configured to.

Additionally, the Custom Application ID is automatically synced when running the `config:sync` command.

Note that this command requires a valid API token. You can get one by using the `mc-scripts login` command.

emmenko · 2022-03-29T12:35:20Z

packages/application-config/src/index.ts

@@ -1,3 +1,4 @@
 export { default as processConfig } from './process-config';
+export { getCustomApplicationConfigPath } from './load-config';


Please also add a separate changeset for the new changes in this package.

emmenko · 2022-03-29T12:35:37Z

packages/application-config/src/transformers.ts

-  const permissionKeys = entryPointUriPathToPermissionKeys(
+  const permissionKeys = entryPointUriPathToResourceAccesses(


emmenko · 2022-03-29T12:40:10Z

packages/mc-scripts/src/bin/cli.js

@@ -44,6 +44,7 @@ Commands:

  login                       Log in to your Merchant Center account through the CLI, using the cloud environment information from the Custom Application config file. An API token is generated and stored in a configuration file for the related cloud environment, and valid for 36 hours.

+  config:sync                 Synchronizes the local custom application config with the one stored on the merchant center cloud. 


Suggested change

config:sync Synchronizes the local custom application config with the one stored on the merchant center cloud.

config:sync Synchronizes the local Custom Application config with the Merchant Center. A new Custom Application will be created if none existed, otherwise it will be updated.

emmenko · 2022-03-29T12:53:52Z

packages/mc-scripts/src/commands/config:sync.js

+  const userOrganizations = await fetchUserOrganizations({ mcApiUrl, token });
+
+  let organizationId, organizationName;
+
+  if (userOrganizations.total > 1) {
+    const organizationChoices = userOrganizations.results.map(
+      (organization) => ({
+        title: organization.name,
+        value: organization.id,
+      })
+    );
+
+    organizationId = await prompts({
+      type: 'select',
+      name: 'organizationId',
+      message: 'Select Organization',
+      choices: organizationChoices,
+      initial: 0,
+    })['organizationId'];
+
+    organizationName = organizationChoices.find(
+      ({ value }) => value === organizationId
+    ).title;
+  } else {
+    organizationId = userOrganizations.results[0].id;
+    organizationName = userOrganizations.results[0].name;
+  }


Prompting for the organization is only required for creating a new Custom App.

If the app exists, we already have the organizationId from the response.

emmenko · 2022-03-29T12:54:55Z

packages/mc-scripts/src/commands/config:sync.js

+    const { confirmation } = await prompts({
+      type: 'text',
+      name: 'confirmation',
+      message: `You are about to create the configuration in the "${organizationName}" organization in environment ${location}. Are you sure you want to proceed?`,


Suggested change

message: `You are about to create the configuration in the "${organizationName}" organization in environment ${location}. Are you sure you want to proceed?`,

message: `You are about to create a new Custom Application in the "${organizationName}" organization for the ${mcApiUrl} environment. Are you sure you want to proceed?`,

Nicola recommendation is great, but bear in mind that perhaps we have an extra "environment" word over there:

You are about to create a new Custom Application in the "${organizationName}" organization for the environment ${mcApiUrl} environment. Are you sure you want to proceed?

Maybe we could use only one:

You are about to create a new Custom Application in the "${organizationName}" organization for the ${mcApiUrl} environment. Are you sure you want to proceed?

Yes thanks, it's a typo.

emmenko · 2022-03-29T12:57:29Z

packages/mc-scripts/src/commands/config:sync.js

+      );
+      console.log(
+        chalk.green(
+          `You have successfully created the configuration in the "${organizationName}" organization in environment ${location}.\nYour local configuration has also been updated with the newly created application identifier: ${createdCustomApplication.id}.\nLink to the created custom application is ${customAppLink}`


Suggested change

`You have successfully created the configuration in the "${organizationName}" organization in environment ${location}.\nYour local configuration has also been updated with the newly created application identifier: ${createdCustomApplication.id}.\nLink to the created custom application is ${customAppLink}`

`Custom Application created.\nThe "applicationId" in your local Custom Application config file has been updated with the application ID.\nYou can see the Custom Application data in the Merchant Center at ${customAppLink}.`

emmenko · 2022-03-29T12:58:53Z

packages/mc-scripts/src/commands/config:sync.js

+  const { confirmation } = await prompts({
+    type: 'text',
+    name: 'confirmation',
+    message: `You are about to update the configuration in the "${organizationName}" organization in environment ${location}. Are you sure you want to proceed?`,


Suggested change

message: `You are about to update the configuration in the "${organizationName}" organization in environment ${location}. Are you sure you want to proceed?`,

message: `You are about to update the Custom Application "${entryPointUriPath}" in the ${mcApiUrl} environment. Are you sure you want to proceed?`,

emmenko · 2022-03-29T13:00:44Z

packages/mc-scripts/src/commands/config:sync.js

+  );
+  console.log(
+    chalk.green(
+      `You have successfully updated the configuration in the "${organizationName}" organization in environment ${location}.\nLink to the created custom application is ${customAppLink}`


Suggested change

`You have successfully updated the configuration in the "${organizationName}" organization in environment ${location}.\nLink to the created custom application is ${customAppLink}`

`You have successfully updated the configuration in the "${organizationName}" organization in environment ${location}.\nLink to the created custom application is ${customAppLink}`

`Custom Application updated.\nYou can see the Custom Application data in the Merchant Center at ${customAppLink}.`

CarlosCortizasCT · 2022-03-29T13:30:50Z

packages/mc-scripts/src/commands/config:sync.js

@@ -0,0 +1,138 @@
+const omit = require('lodash/omit');
+const prompts = require('prompts');
+const chalk = require('react-dev-utils/chalk');


Here we are relying in the fact that react-dev-utils dependency currently export chalk.
Given that we are going to use that dependency directly I guess it would be safer to explicitly depend on it by itself declaring it in our package.json.

CarlosCortizasCT · 2022-03-29T13:32:47Z

packages/mc-scripts/src/commands/config:sync.js

+      initial: 'yes',
+    });
+    if (confirmation.toLowerCase().charAt(0) !== 'y') {
+      console.log('Aborted.');


Perhaps we could use chalk (red?) here to be more explicit with the message.

CarlosCortizasCT · 2022-03-29T13:36:08Z

packages/mc-scripts/src/commands/config:sync.js

+    initial: 'yes',
+  });
+  if (confirmation.toLowerCase().charAt(0) !== 'y') {
+    console.log('Aborted.');


Perhaps we could use chalk (red?) here to be more explicit with the message.

CarlosCortizasCT · 2022-03-29T13:36:57Z

packages/mc-scripts/src/commands/config:sync.js

+};
+
+configSync().catch((error) => {
+  console.error(error);


Perhaps we could use chalk (red?) here to be more explicit with the message.

CarlosCortizasCT · 2022-03-29T14:00:38Z

packages/mc-scripts/src/utils/update-application-id-in-custom-application-config.js

+  getCustomApplicationConfigPath,
+} = require('@commercetools-frontend/application-config');
+
+function updateApplicationIdInCustomApplicationConfig(applicationId) {


I was wondering if we could maybe just update the applicationId using a regular expression to make this process simpler.

Maybe something like:

configFileContents.replace(/("env":.*"production":.*"applicationId":\s?)"(\w*)"/, '$1"[REPLACER]"')

(perhaps this is more complex than I can see)

FYI: we use this also int he create-mc-app CLI, as we need to update more fields.

https://github.com/commercetools/merchant-center-application-kit/blob/main/packages/create-mc-app/src/tasks/update-custom-application-config.js

Also to note, that this is only for JS files. For JSON we can update it directly. @Rhotimee I think I mentioned this last time but I forgot to follow up with you. We need to adjust the update logic in case the config is a JSON file.

…custom application

…missionKeys

…rmissionKeys

…application-config package

Rhotimee · 2022-03-30T15:15:56Z

@emmenko @CarlosCortizasCT, thanks for the feedback. All feedback above has been Implemented. Kindly take another look.

emmenko

Awesome, looks much better now thanks!

Just a few minor adjustments and then we're good to go 🚀

emmenko · 2022-03-30T19:22:19Z

.changeset/tidy-zoos-applaud.md

+'@commercetools-frontend/application-config': minor
+---
+
+Implement and expose getConfigPath


Suggested change

Implement and expose getConfigPath

Expose a new function `getConfigPath` to return the absolute file path of the Custom Application config file.

emmenko · 2022-03-30T19:27:36Z

packages/mc-scripts/src/commands/config:sync.js

+    if (userOrganizations.total > 1) {
+      const organizationChoices = userOrganizations.results.map(
+        (organization) => ({
+          title: organization.name,
+          value: organization.id,
+        })
+      );
+
+      organizationId = await prompts({
+        type: 'select',
+        name: 'organizationId',
+        message: 'Select Organization',
+        choices: organizationChoices,
+        initial: 0,
+      })['organizationId'];
+
+      organizationName = organizationChoices.find(
+        ({ value }) => value === organizationId
+      ).title;
+    } else {
+      organizationId = userOrganizations.results[0].id;
+      organizationName = userOrganizations.results[0].name;
+    }


I would also check if there are no organizations. In this case we need to throw an error.

And maybe invert the condition.

Suggested change

if (userOrganizations.total > 1) {

const organizationChoices = userOrganizations.results.map(

(organization) => ({

title: organization.name,

value: organization.id,

})

);

organizationId = await prompts({

type: 'select',

name: 'organizationId',

message: 'Select Organization',

choices: organizationChoices,

initial: 0,

})['organizationId'];

organizationName = organizationChoices.find(

({ value }) => value === organizationId

).title;

} else {

organizationId = userOrganizations.results[0].id;

organizationName = userOrganizations.results[0].name;

}

if (userOrganizations.total === 0) {

throw new Error(`It seems you are not an admin of any Organization. Please make sure to be part of the Administrators team of the Organization you want the Custom Application to be configured to.`);

}

if (userOrganizations.total === 1) {

organizationId = userOrganizations.results[0].id;

organizationName = userOrganizations.results[0].name;

} else {

const organizationChoices = userOrganizations.results.map(

(organization) => ({

title: organization.name,

value: organization.id,

})

);

organizationId = await prompts({

type: 'select',

name: 'organizationId',

message: 'Select Organization',

choices: organizationChoices,

initial: 0,

})['organizationId'];

organizationName = organizationChoices.find(

({ value }) => value === organizationId

).title;

}

emmenko · 2022-03-30T19:32:10Z

packages/mc-scripts/src/utils/graphql-requests.js

+      'x-graphql-target': target,
+      'x-mc-cli-access-token': token,
+      'x-user-agent': userAgent,


Suggested change

'x-graphql-target': target,

'x-mc-cli-access-token': token,

'x-user-agent': userAgent,

Accept: 'application/json',

'Content-Type': 'application/json',

'x-graphql-target': target,

'x-mc-cli-access-token': token,

'x-user-agent': userAgent,

emmenko · 2022-03-30T19:33:03Z

packages/mc-scripts/src/utils/graphql-requests.js

@@ -0,0 +1,113 @@
+const { GraphQLClient } = require('graphql-request');
+const { GRAPHQL_TARGETS } = require('@commercetools-frontend/constants');


Please define this dependency in the package.json.

emmenko · 2022-03-30T19:34:51Z

packages/mc-scripts/src/utils/update-application-id-in-custom-application-config.js

+    customApplicationConfig.env.production.applicationId = applicationId;
+    fs.writeFileSync(
+      filePath,
+      JSON.stringify(customApplicationConfig, null, 2),


Let's format this with Prettier as well.

emmenko · 2022-03-30T19:36:25Z

website/src/content/api-reference/cli.mdx

+
+If a new Custom Application needs to be created, an interactive prompt will ask the user to select the Organization where the Custom Application should be configured to.
+
+Additionally, the Custom Application ID is automatically synced when running the `config:sync` command.


Suggested change

Additionally, the Custom Application ID is automatically synced when running the `config:sync` command.

Additionally, the [Custom Application ID](/api-reference/application-config#envproductionapplicationid) is automatically synced when running the `config:sync` command.

emmenko · 2022-03-30T19:37:06Z

website/src/content/api-reference/cli.mdx

+```console
+mc-scripts config:sync
+```
+-->


Suggested change

-->

<Info>

The command uses the [cloud Region](/concepts/merchant-center-api#cloud-regions) environment information from the Custom Application config.

</Info>

-->

CarlosCortizasCT · 2022-03-31T08:35:27Z

packages/mc-scripts/src/commands/config:sync.js

+  // update applicationID in the custom-application-config file
+  updateApplicationIdInCustomApplicationConfig(
+    fetchedCustomApplication.application.id
+  );


Is it actually possible for the ID of a Custom Application to change after its creation?

Not to my knowledge. It's a Prisma generated cuid.

No. But, it is possible that the user created the custom app on the merchant center and not with the cli.

The function is to update the local custom-application-config with the applicationId.

Speaking of the applicationId, we need to consider this use case: the config might use an env placeholder for the application id, e.g. ${env:APPLICATION_ID}.

In this case, we can't really replace the value.

I suppose we should only do that when we create a new Custom App. When updating, we shouldn't rewrite the value.

@Rhotimee Could you adjust the logic? Thanks

sure 👍🏽

CarlosCortizasCT

lgtm

…dating config

emmenko · 2022-03-31T15:31:13Z

I noticed that the build bundle does not contain the .graphql files. I'll push a commit to fix that.

I'll also add a --dry-run option to help testing the command.

emmenko

💯 🚀

packages/mc-scripts/src/commands/config:sync.js

… process

kark

Awesome work 👏

vercel bot temporarily deployed to Preview March 24, 2022 15:33 Inactive

vercel bot temporarily deployed to Preview March 25, 2022 12:05 Inactive

vercel bot temporarily deployed to Preview March 25, 2022 12:24 Inactive

Rhotimee force-pushed the SHIELD-448-mc-script-config-sync branch from 04055fb to e700bc8 Compare March 25, 2022 12:35

vercel bot had a problem deploying to Preview March 25, 2022 12:35 Failure

vercel bot temporarily deployed to Preview March 25, 2022 12:42 Inactive

vercel bot temporarily deployed to Preview March 28, 2022 16:30 Inactive

vercel bot temporarily deployed to Preview March 28, 2022 16:36 Inactive

vercel bot temporarily deployed to Preview March 28, 2022 16:59 Inactive

Rhotimee marked this pull request as ready for review March 28, 2022 16:59

Rhotimee requested a review from a team March 28, 2022 17:00

vercel bot temporarily deployed to Preview March 29, 2022 11:37 Inactive

emmenko reviewed Mar 29, 2022

View reviewed changes

CarlosCortizasCT reviewed Mar 29, 2022

View reviewed changes

vercel bot temporarily deployed to Preview March 30, 2022 14:37 Inactive

Rhotimee added 9 commits March 30, 2022 16:40

feat: (shield-448): implement config:sync first draft

8c9b234

feat(config-sync): send requests for fetching, creating and updating …

4c8607c

…custom application

feat(config-sync): add generated graphql

b083469

feat(config-sync): add tests for graphql requests

1c728ab

feat(config-sync): update custom application config with applicationId

14497b6

chore(config-sync): update docs, add changeset

8a052eb

chore(config-sync): revert transformers to use entryPointUriPathToPer…

ba815ca

…missionKeys

chore(process-config): use entryPointUriPathToResourceAccesses for pe…

7a82809

…rmissionKeys

refactor(application-config): move getCustomApplicationConfigPath to …

85ac94d

…application-config package

Rhotimee added 4 commits March 30, 2022 16:42

refactor(config-sync): update generated types

02dd95d

refactor(config-sync): use chalk directly

3fc501c

feat(config-sync): implement .json config update

3fbbb8c

feat(config-sync): rename graphql query

db8d013

Rhotimee force-pushed the SHIELD-448-mc-script-config-sync branch from f1e7128 to db8d013 Compare March 30, 2022 14:42

vercel bot had a problem deploying to Preview March 30, 2022 14:42 Failure

refactor(config-sync): declare graphql file outside the function

fa61b58

vercel bot temporarily deployed to Preview March 30, 2022 14:59 Inactive

emmenko reviewed Mar 30, 2022

View reviewed changes

CarlosCortizasCT reviewed Mar 31, 2022

View reviewed changes

refactor(config-sync): update messages, docs and cleanup

c5d0b92

vercel bot temporarily deployed to Preview March 31, 2022 08:58 Inactive

CarlosCortizasCT approved these changes Mar 31, 2022

View reviewed changes

refactor(config-sync): avoid updating applicationId in config when up…

1e849cc

…dating config

vercel bot temporarily deployed to Preview March 31, 2022 10:08 Inactive

emmenko added 2 commits March 31, 2022 17:52

fix(mc-scripts): copy graphql files to build output

8e58b32

refactor(mc-scripts): better error handling

714f025

vercel bot temporarily deployed to Preview March 31, 2022 15:53 Inactive

docs: update changeset

d648cd2

vercel bot temporarily deployed to Preview April 1, 2022 07:29 Inactive

emmenko approved these changes Apr 1, 2022

View reviewed changes

kark reviewed Apr 1, 2022

View reviewed changes

packages/mc-scripts/src/commands/config:sync.js Outdated Show resolved Hide resolved

refactor(config-sync): ensure aborted is logged when user cancels the…

fe05ab7

… process

vercel bot temporarily deployed to Preview April 1, 2022 08:57 Inactive

kark approved these changes Apr 1, 2022

View reviewed changes

Rhotimee merged commit ea1bee4 into main Apr 1, 2022

Rhotimee deleted the SHIELD-448-mc-script-config-sync branch April 1, 2022 09:19

ghost mentioned this pull request Apr 1, 2022

Version Packages #2516

Merged

		@@ -1,3 +1,4 @@
		export { default as processConfig } from './process-config';
		export { getCustomApplicationConfigPath } from './load-config';

		const permissionKeys = entryPointUriPathToPermissionKeys(
		const permissionKeys = entryPointUriPathToResourceAccesses(

		@@ -44,6 +44,7 @@ Commands:

		login Log in to your Merchant Center account through the CLI, using the cloud environment information from the Custom Application config file. An API token is generated and stored in a configuration file for the related cloud environment, and valid for 36 hours.

		config:sync Synchronizes the local custom application config with the one stored on the merchant center cloud.

	message: `You are about to create the configuration in the "${organizationName}" organization in environment ${location}. Are you sure you want to proceed?`,
	message: `You are about to create a new Custom Application in the "${organizationName}" organization for the ${mcApiUrl} environment. Are you sure you want to proceed?`,

	`You have successfully created the configuration in the "${organizationName}" organization in environment ${location}.\nYour local configuration has also been updated with the newly created application identifier: ${createdCustomApplication.id}.\nLink to the created custom application is ${customAppLink}`
	`Custom Application created.\nThe "applicationId" in your local Custom Application config file has been updated with the application ID.\nYou can see the Custom Application data in the Merchant Center at ${customAppLink}.`

	message: `You are about to update the configuration in the "${organizationName}" organization in environment ${location}. Are you sure you want to proceed?`,
	message: `You are about to update the Custom Application "${entryPointUriPath}" in the ${mcApiUrl} environment. Are you sure you want to proceed?`,

	`You have successfully updated the configuration in the "${organizationName}" organization in environment ${location}.\nLink to the created custom application is ${customAppLink}`
	`You have successfully updated the configuration in the "${organizationName}" organization in environment ${location}.\nLink to the created custom application is ${customAppLink}`
	`Custom Application updated.\nYou can see the Custom Application data in the Merchant Center at ${customAppLink}.`

	Implement and expose getConfigPath
	Expose a new function `getConfigPath` to return the absolute file path of the Custom Application config file.

		@@ -0,0 +1,113 @@
		const { GraphQLClient } = require('graphql-request');
		const { GRAPHQL_TARGETS } = require('@commercetools-frontend/constants');


		If a new Custom Application needs to be created, an interactive prompt will ask the user to select the Organization where the Custom Application should be configured to.

		Additionally, the Custom Application ID is automatically synced when running the `config:sync` command.

	Additionally, the Custom Application ID is automatically synced when running the `config:sync` command.
	Additionally, the [Custom Application ID](/api-reference/application-config#envproductionapplicationid) is automatically synced when running the `config:sync` command.

--->
+<Info>
+The command uses the [cloud Region](/concepts/merchant-center-api#cloud-regions) environment information from the Custom Application config.
+</Info>
+-->

feat: add new mc-scripts config:sync command #2524

feat: add new mc-scripts config:sync command #2524

Conversation

Rhotimee commented Mar 24, 2022 • edited by emmenko Loading

changeset-bot bot commented Mar 24, 2022 • edited Loading

🦋 Changeset detected

vercel bot commented Mar 24, 2022 • edited Loading

emmenko 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

emmenko Mar 29, 2022 • 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

CarlosCortizasCT Mar 29, 2022 • 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

Rhotimee commented Mar 30, 2022

emmenko 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

CarlosCortizasCT left a comment

Choose a reason for hiding this comment

emmenko commented Mar 31, 2022

emmenko left a comment

Choose a reason for hiding this comment

kark left a comment

Choose a reason for hiding this comment

feat: add new `mc-scripts config:sync` command #2524

feat: add new `mc-scripts config:sync` command #2524

Rhotimee commented Mar 24, 2022 •

edited by emmenko

Loading

changeset-bot bot commented Mar 24, 2022 •

edited

Loading

vercel bot commented Mar 24, 2022 •

edited

Loading

emmenko Mar 29, 2022 •

edited

Loading

CarlosCortizasCT Mar 29, 2022 •

edited

Loading