feat(localized-multiline-text-input): add support for isCondensed pro… #2793

Sarah4VT · 2024-04-23T20:13:17Z

…perty on LocalizedMultilineTextInput

Summary

Adds support for isCondensed prop on LocalizedMultilineTextInput component to display a condensed layout.

Description

Figma Design

Results with isCondensed toggled on

changeset-bot · 2024-04-23T20:13:22Z

🦋 Changeset detected

Latest commit: a7a114f

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

This PR includes changesets to release 96 packages

Name	Type
@commercetools-uikit/localized-multiline-text-input	Minor
@commercetools-uikit/localized-text-input	Minor
@commercetools-uikit/input-utils	Minor
@commercetools-uikit/localized-multiline-text-field	Minor
@commercetools-uikit/inputs	Minor
@commercetools-uikit/localized-text-field	Minor
@commercetools-uikit/calendar-utils	Minor
@commercetools-uikit/checkbox-input	Minor
@commercetools-uikit/localized-money-input	Minor
@commercetools-uikit/localized-rich-text-input	Minor
@commercetools-uikit/money-input	Minor
@commercetools-uikit/multiline-text-input	Minor
@commercetools-uikit/number-input	Minor
@commercetools-uikit/password-input	Minor
@commercetools-uikit/radio-input	Minor
@commercetools-uikit/rich-text-input	Minor
@commercetools-uikit/rich-text-utils	Minor
@commercetools-uikit/search-text-input	Minor
@commercetools-uikit/selectable-search-input	Minor
@commercetools-uikit/text-input	Minor
@commercetools-uikit/time-input	Minor
@commercetools-uikit/toggle-input	Minor
@commercetools-uikit/fields	Minor
@commercetools-frontend/ui-kit	Minor
@commercetools-uikit/date-input	Minor
@commercetools-uikit/date-range-input	Minor
@commercetools-uikit/date-time-input	Minor
@commercetools-uikit/money-field	Minor
@commercetools-uikit/multiline-text-field	Minor
@commercetools-uikit/pagination	Minor
@commercetools-uikit/number-field	Minor
@commercetools-uikit/password-field	Minor
@commercetools-uikit/data-table-manager	Minor
@commercetools-uikit/radio-field	Minor
@commercetools-uikit/text-field	Minor
@commercetools-uikit/time-field	Minor
@commercetools-uikit/date-field	Minor
@commercetools-uikit/date-range-field	Minor
@commercetools-uikit/date-time-field	Minor
@commercetools-uikit/design-system	Minor
@commercetools-uikit/calendar-time-utils	Minor
@commercetools-uikit/hooks	Minor
@commercetools-uikit/i18n	Minor
@commercetools-uikit/localized-utils	Minor
@commercetools-uikit/utils	Minor
@commercetools-uikit/accessible-hidden	Minor
@commercetools-uikit/avatar	Minor
@commercetools-uikit/card	Minor
@commercetools-uikit/collapsible-motion	Minor
@commercetools-uikit/collapsible-panel	Minor
@commercetools-uikit/collapsible	Minor
@commercetools-uikit/constraints	Minor
@commercetools-uikit/data-table	Minor
@commercetools-uikit/field-errors	Minor
@commercetools-uikit/field-label	Minor
@commercetools-uikit/field-warnings	Minor
@commercetools-uikit/grid	Minor
@commercetools-uikit/icons	Minor
@commercetools-uikit/label	Minor
@commercetools-uikit/link	Minor
@commercetools-uikit/loading-spinner	Minor
@commercetools-uikit/messages	Minor
@commercetools-uikit/notifications	Minor
@commercetools-uikit/primary-action-dropdown	Minor
@commercetools-uikit/progress-bar	Minor
@commercetools-uikit/stamp	Minor
@commercetools-uikit/tag	Minor
@commercetools-uikit/text	Minor
@commercetools-uikit/tooltip	Minor
@commercetools-uikit/view-switcher	Minor
@commercetools-uikit/accessible-button	Minor
@commercetools-uikit/flat-button	Minor
@commercetools-uikit/icon-button	Minor
@commercetools-uikit/link-button	Minor
@commercetools-uikit/primary-button	Minor
@commercetools-uikit/secondary-button	Minor
@commercetools-uikit/secondary-icon-button	Minor
@commercetools-uikit/dropdown-menu	Minor
@commercetools-uikit/async-creatable-select-field	Minor
@commercetools-uikit/async-select-field	Minor
@commercetools-uikit/creatable-select-field	Minor
@commercetools-uikit/search-select-field	Minor
@commercetools-uikit/select-field	Minor
@commercetools-uikit/async-creatable-select-input	Minor
@commercetools-uikit/async-select-input	Minor
@commercetools-uikit/creatable-select-input	Minor
@commercetools-uikit/search-select-input	Minor
@commercetools-uikit/select-input	Minor
@commercetools-uikit/select-utils	Minor
@commercetools-uikit/spacings-inline	Minor
@commercetools-uikit/spacings-inset-squish	Minor
@commercetools-uikit/spacings-inset	Minor
@commercetools-uikit/spacings-stack	Minor
@commercetools-uikit/buttons	Minor
@commercetools-uikit/spacings	Minor
visual-testing-app	Patch

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 · 2024-04-23T20:13:24Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
ui-kit	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 26, 2024 0:58am

Sarah4VT · 2024-04-23T20:36:22Z

@CarlosCortizasCT There is some weirdness with this one that I can't figure out. I'm not sure if it has to do with the 3rd party library that we use for this resizable text area. But this !important style for height is getting set somewhere that I think may be calculated based on the initial rendering. This means if you toggle isCondensed in storybook, it doesn't recalculate. Not sure if this is something I need to handle? I did confirm if I have isCondensed turned on, and refresh storybook, it does render the inputs correctly. 🤷‍♀️

kark · 2024-04-24T11:11:21Z

@CarlosCortizasCT There is some weirdness with this one that I can't figure out. I'm not sure if it has to do with the 3rd party library that we use for this resizable text area. But this !important style for height is getting set somewhere that I think may be calculated based on the initial rendering. This means if you toggle isCondensed in storybook, it doesn't recalculate. Not sure if this is something I need to handle? I did confirm if I have isCondensed turned on, and refresh storybook, it does render the inputs correctly. 🤷‍♀️

@Sarah4VT After investigating this case, it appears that the observed behavior results from the underlying <TextareaAutosize> component from the external library, as you mentioned. More precisely, we've set cacheMeasurements={true}

ui-kit/packages/components/inputs/input-utils/src/multiline-input/multiline-input.tsx

Line 106 in 2c9b378

cacheMeasurements={true}

which prevents re-renders. In my view, it's very unlikely for the isCondensed prop to change once this component is rendered, so I think this behavior is negligible.
Another option is switching to cacheMeasurements={false} but I'm not sure if this might cause any issues.

@commercetools/shield-team-design-system what is your take on that?

chloe0592 · 2024-04-24T11:30:13Z

I'm wondering if we actually need the cacheMeasurements={true} prop. I removed it and tested out a bit, and it seems to me it doesn't have any side effects and it solves the highlighted UI issue. 🤔

ddouglasz · 2024-04-24T11:31:01Z

@commercetools/shield-team-design-system what is your take on that?

Thank you Kacper, I noticed it too and was playing around with it a little bit to be sure if switching it to false actually causes any issues. At least, so far, I have not noticed any issues.
The documentation defines the prop to Reuse previously computed measurements when computing height of textarea which seems to stop the height from updating.

Sarah4VT · 2024-04-24T13:39:54Z

@commercetools/shield-team-design-system I went ahead and removed the cacheMeasurements value and tested it in storybook and verified that it does allow the size to update when toggling the isCondensed property now in storybook. Hopefully this does the trick. Thanks for the suggestion!

ddouglasz

Looks good now 💯
Thank you @Sarah4VT

CarlosCortizasCT · 2024-04-24T14:46:55Z

Thank you all for looking into this.

As you already spotted, the issue is because of the usage of the cacheMeasurements props which is used to enhance the TextareaAutosize performance by avoiding going to the DOM to perform the measurements calculations needed as it's an "expensive" operation that will happen in every render otherwise (eg: typing anything in the input).
I'm not sure how "expensive" this operation can be; maybe it could be seen in low-end devices.

I can think of different options for use to consider:

Do nothing: In this case we assume (as @kark mentioned) is very unlikely the value of the isCondensed prop will change after the component is rendered, so it would be ok to accept the new behaviour.
- In this case I would say consumers can be confused when coming to our Storybook and seeing that prop does nothing on the component and this is something we want to avoid.
Expose a prop to control that behaviour: Let's expose the cacheMeasurements as part of the component's API and set it to true by default. We can explain in the docs of that prop where it can be useful to use it (We would be using it in our Storybook story so the component reacts to changing the isCondensed knob).
Keep track of the isCondensed prop history in the MultilineInput component: if we have a ref in that component with the last isConsensed valued, we can compare it with the new one and, only if it has changed, we set the cacheMeasurements to false.

Personally I would try to avoid removing that property altogether from the MultilineInput components because it will introduce a performance degradation from our baseline.
I believe exposing the cacheMeasurements property and having it to true by default is the most convenient solution.

Sarah4VT · 2024-04-24T15:19:53Z

Thank you all for looking into this.

As you already spotted, the issue is because of the usage of the cacheMeasurements props which is used to enhance the TextareaAutosize performance by avoiding going to the DOM to perform the measurements calculations needed as it's an "expensive" operation that will happen in every render otherwise (eg: typing anything in the input). I'm not sure how "expensive" this operation can be; maybe it could be seen in low-end devices.

I can think of different options for use to consider:
* **Do nothing**: In this case we assume (as @kark mentioned) is very unlikely the value of the `isCondensed` prop will change after the component is rendered, so it would be ok to accept the new behaviour.
  
  * In this case I would say consumers can be confused when coming to our Storybook and seeing that prop does nothing on the component and this is something we want to avoid.

* **Expose a prop to control that behaviour**: Let's expose the `cacheMeasurements` as part of the component's API and set it to `true` by default. We can explain in the docs of that prop where it can be useful to use it (We would be using it in our Storybook story so the component reacts to changing the `isCondensed` knob).

* **Keep track of the `isCondensed` prop history in the `MultilineInput` component**: if we have a ref in that component with the last `isConsensed` valued, we can compare it with the new one and, only if it has changed, we set the `cacheMeasurements` to `false`.
Personally I would try to avoid removing that property altogether from the MultilineInput components because it will introduce a performance degradation from our baseline. I believe exposing the cacheMeasurements property and having it to true by default is the most convenient solution.

Thanks for the feedback Carlos! I agree, I was nervous to take it out, because it was obviously added for a reason and I didn't want to lose any benefits it was giving, or break some functionality we depended on.

I agree that the 2nd proposed solution could work fine, but I actually thought your 3rd solution was a little more encapsulated and took mental load off of consuming components to understand when and how to set that. Right now, we know what our one use case is for needing this value turned off, and that's in Storybook if we are toggling this value. In theory if someone else wanted to toggle this value (which I agree is very unlikely), why not handle it for them since we have to handle it for ourselves anyways. I went ahead and implemented a fix based on these thoughts. Take a look, see if you like it. If not, I can undo it and add a different solution that will match your second proposal.

ddouglasz

Some minor feedback it we would be going with this approach.

ddouglasz · 2024-04-25T07:17:36Z

packages/components/inputs/input-utils/src/multiline-input/multiline-input.tsx

@@ -52,6 +59,20 @@ const MultilineInput = (props: TMultiLineInputProps) => {
  const { onHeightChange } = props;
  const ref = useRef<HTMLTextAreaElement | null>(null);

+  const [prevIsCondensed, setPrevIsCondensed] = useState(props.isCondensed);
+  const [cacheMeasurements, setCacheMeasurements] = useState(true);


Suggested change

const [cacheMeasurements, setCacheMeasurements] = useState(true);

const [isCacheMeasurements, setIsCacheMeasurements] = useState(true);

ddouglasz · 2024-04-25T07:18:01Z

packages/components/inputs/input-utils/src/multiline-input/multiline-input.tsx

+    // cacheMeasurements is set to false. So let's set cacheMeasurements to true by default to get the performance
+    // benefits, unless isCondensed value has changed, in which case we will set it to false for this render.
+    if (props.isCondensed !== prevIsCondensed) {
+      setCacheMeasurements(false);


Suggested change

setCacheMeasurements(false);

setIsCacheMeasurements(false);

ddouglasz · 2024-04-25T07:18:50Z

packages/components/inputs/input-utils/src/multiline-input/multiline-input.tsx

+    if (props.isCondensed !== prevIsCondensed) {
+      setCacheMeasurements(false);
+    } else {
+      setCacheMeasurements(true);


Suggested change

setCacheMeasurements(true);

setIsCacheMeasurements(true);

ddouglasz · 2024-04-25T07:19:05Z

packages/components/inputs/input-utils/src/multiline-input/multiline-input.tsx

@@ -103,7 +124,7 @@ const MultilineInput = (props: TMultiLineInputProps) => {
      role="textbox"
      minRows={MIN_ROW_COUNT}
      maxRows={props.isOpen ? undefined : MIN_ROW_COUNT}
-      cacheMeasurements={true}
+      cacheMeasurements={cacheMeasurements}


Suggested change

cacheMeasurements={cacheMeasurements}

cacheMeasurements={isCacheMeasurements}

CarlosCortizasCT · 2024-04-25T07:24:43Z

Thanks @Sarah4VT for your feedback 👍

In theory if someone else wanted to toggle this value (which I agree is very unlikely), why not handle it for them since we have to handle it for ourselves anyways.

My argument to avoid this is that any lines of code we add to a component increases its complexity and, thus, its maintainability.
I believe we should balance that with the features we provide and, in this case, since we (more or less) agree is unlikely consumers would need that, exposing the property would be (in my opinion) a good balance between complexity added to the component in comparison with the requirement.

kterry1

Nice work! Tested it on the preview branch and it works as expected.

Sarah4VT · 2024-04-25T18:14:45Z

Thanks @Sarah4VT for your feedback 👍

In theory if someone else wanted to toggle this value (which I agree is very unlikely), why not handle it for them since we have to handle it for ourselves anyways.

My argument to avoid this is that any lines of code we add to a component increases its complexity and, thus, its maintainability. I believe we should balance that with the features we provide and, in this case, since we (more or less) agree is unlikely consumers would need that, exposing the property would be (in my opinion) a good balance between complexity added to the component in comparison with the requirement.

@CarlosCortizasCT I made the changes to move cacheMeasurements out to a prop on the component to allow ultimate control for consumers and set it to true by default. Let me know if I need to change anything else!

…perty on LocalizedMultilineTextInput

…ensed by reducing value padding and label line height

…llow toggling isCondensed property to affect input height immediately

…based on whether isCondensed value has been toggled

…exposed on LocalizedMultilineTextInput

Sarah4VT · 2024-04-25T18:21:18Z

Some minor feedback it we would be going with this approach.

I ended up undoing the implementation due to Carlos's feedback, so these changes were not applied as the code was removed.

CarlosCortizasCT · 2024-04-25T19:07:16Z

I ended up undoing the implementation due to Carlos's feedback, so these changes were not applied as the code was removed.

Thanks @Sarah4VT 🙇

I've just pushed a small commit in order to use the component's default props better.

Also, bear in mind we're currently not respecting the expected left margin of the text input value when the component is in condensed mode.

Design

Storybook

Sarah4VT · 2024-04-25T19:29:49Z

...components/inputs/localized-multiline-text-input/src/localized-multiline-text-input.story.js

@@ -69,7 +69,7 @@ storiesOf('Components|Inputs', module)
              }
              defaultExpandMultilineText={defaultExpandMultilineText}
              isAutofocussed={boolean('isAutofocussed', false)}
-              cacheMeasurements={boolean('cacheMeasurements', true)}
+              cacheMeasurements={boolean('cacheMeasurements', false)}


@CarlosCortizasCT Do you typically set the default value in storybook to false even if the default value in the component is true?

I think it's better to use false here because, otherwise, the isCondensed check won't work and users won't know why.

…put back to original value and only reduce top/bottom padding when isCondensed

Sarah4VT · 2024-04-25T19:37:26Z

I ended up undoing the implementation due to Carlos's feedback, so these changes were not applied as the code was removed.

Thanks @Sarah4VT 🙇

I've just pushed a small commit in order to use the component's default props better.

Also, bear in mind we're currently not respecting the expected left margin of the text input value when the component is in condensed mode.

Design

Storybook

@CarlosCortizasCT I fixed the left/right padding to go back to the original value and only reduced the top/bottom padding on the input when isCondensed is true. Good catch!

FilPob · 2024-04-26T07:22:32Z

Thanks for all the work! Looks good from my side

CarlosCortizasCT · 2024-04-26T07:22:34Z

Something that I wanted to check with @FilPob is the horizontal padding on the text in the input.
In the Figma file, this padding is 16px but we already had 8px in the component. I think this was wrong as the other inputs also use 16px.

I think we should take the opportunity to also adjust that.

Filip, what do you think?

FilPob · 2024-04-26T07:33:49Z

@CarlosCortizasCT true! good catch. should be 16px for all inputs

… 16px to match other inputs, regardless of isCondensed

Sarah4VT · 2024-04-26T12:56:50Z

@CarlosCortizasCT true! good catch. should be 16px for all inputs

@CarlosCortizasCT @FilPob I made the change to update the horizontal padding and updated the screenshot in the description.

FilPob · 2024-04-26T13:08:31Z

@Sarah4VT awesome, looks good. thanks :)

CarlosCortizasCT

Looks good to me 👍

Thanks Sarah!

Sarah4VT self-assigned this Apr 23, 2024

vercel bot deployed to Preview April 23, 2024 20:33 View deployment

Sarah4VT marked this pull request as ready for review April 23, 2024 20:38

Sarah4VT requested a review from a team April 23, 2024 20:38

Sarah4VT mentioned this pull request Apr 23, 2024

Pangolin 3766 localized multiline text field #2794

Merged

Sarah4VT requested review from a team, jmcreasman, kterry1 and valoriecarli and removed request for a team April 23, 2024 20:57

Sarah4VT force-pushed the PANGOLIN-3739-localized-multiline-text-input branch from e59adec to 0183476 Compare April 24, 2024 13:40

vercel bot deployed to Preview April 24, 2024 13:44 View deployment

ddouglasz approved these changes Apr 24, 2024

View reviewed changes

vercel bot deployed to Preview April 24, 2024 15:17 View deployment

Sarah4VT force-pushed the PANGOLIN-3739-localized-multiline-text-input branch from 308fec2 to 13593a2 Compare April 24, 2024 19:25

vercel bot deployed to Preview April 24, 2024 19:27 View deployment

ddouglasz reviewed Apr 25, 2024

View reviewed changes

kterry1 approved these changes Apr 25, 2024

View reviewed changes

Sarah4VT force-pushed the PANGOLIN-3739-localized-multiline-text-input branch from 13593a2 to 16d0263 Compare April 25, 2024 18:12

Sarah4VT added 5 commits April 25, 2024 14:15

feat(localized-multiline-text-input): add support for isCondensed pro…

9eb022d

…perty on LocalizedMultilineTextInput

feat(localized-multiline-text-input): fix height of input when isCond…

af16825

…ensed by reducing value padding and label line height

feat(localized-multiline-text-input): turn cacheMeasurements off to a…

f7dcdce

…llow toggling isCondensed property to affect input height immediately

feat(localized-multiline-text-input): set value of cacheMeasurements …

c4f6dce

…based on whether isCondensed value has been toggled

feat(localized-multiline-text-input): move cacheMeasurements to prop …

13dbaf4

…exposed on LocalizedMultilineTextInput

Sarah4VT force-pushed the PANGOLIN-3739-localized-multiline-text-input branch from 16d0263 to 13dbaf4 Compare April 25, 2024 18:15

vercel bot deployed to Preview April 25, 2024 18:17 View deployment

refactor(localized-multiline-text-input): use components default props

97dbeec

vercel bot deployed to Preview April 25, 2024 19:06 View deployment

Sarah4VT commented Apr 25, 2024

View reviewed changes

feat(localized-multiline-text-input): revert left/right padding on in…

913ee8b

…put back to original value and only reduce top/bottom padding when isCondensed

vercel bot deployed to Preview April 25, 2024 19:37 View deployment

CarlosCortizasCT requested a review from FilPob April 26, 2024 07:16

FilPob approved these changes Apr 26, 2024

View reviewed changes

Merge branch 'main' into PANGOLIN-3739-localized-multiline-text-input

2a54ca7

vercel bot deployed to Preview April 26, 2024 09:18 View deployment

feat(localized-multiline-text-input): change horizontal padding to be…

a7a114f

… 16px to match other inputs, regardless of isCondensed

vercel bot deployed to Preview April 26, 2024 12:58 View deployment

Sarah4VT requested a review from CarlosCortizasCT April 26, 2024 13:45

CarlosCortizasCT approved these changes Apr 29, 2024

View reviewed changes

CarlosCortizasCT merged commit d72e043 into main Apr 29, 2024
7 checks passed

CarlosCortizasCT deleted the PANGOLIN-3739-localized-multiline-text-input branch April 29, 2024 07:57

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(localized-multiline-text-input): add support for isCondensed pro… #2793

feat(localized-multiline-text-input): add support for isCondensed pro… #2793

Sarah4VT commented Apr 23, 2024 •

edited

Loading

changeset-bot bot commented Apr 23, 2024 •

edited

Loading

vercel bot commented Apr 23, 2024 •

edited

Loading

Sarah4VT commented Apr 23, 2024 •

edited

Loading

kark commented Apr 24, 2024

chloe0592 commented Apr 24, 2024

ddouglasz commented Apr 24, 2024

Sarah4VT commented Apr 24, 2024

ddouglasz left a comment

CarlosCortizasCT commented Apr 24, 2024 •

edited

Loading

Sarah4VT commented Apr 24, 2024

ddouglasz left a comment

ddouglasz Apr 25, 2024

ddouglasz Apr 25, 2024

ddouglasz Apr 25, 2024

ddouglasz Apr 25, 2024

CarlosCortizasCT commented Apr 25, 2024 •

edited

Loading

kterry1 left a comment

Sarah4VT commented Apr 25, 2024

Sarah4VT commented Apr 25, 2024

CarlosCortizasCT commented Apr 25, 2024

Sarah4VT Apr 25, 2024

CarlosCortizasCT Apr 26, 2024

Sarah4VT commented Apr 25, 2024

FilPob commented Apr 26, 2024

CarlosCortizasCT commented Apr 26, 2024

FilPob commented Apr 26, 2024

Sarah4VT commented Apr 26, 2024

FilPob commented Apr 26, 2024

CarlosCortizasCT left a comment

	const [cacheMeasurements, setCacheMeasurements] = useState(true);
	const [isCacheMeasurements, setIsCacheMeasurements] = useState(true);

	cacheMeasurements={cacheMeasurements}
	cacheMeasurements={isCacheMeasurements}

feat(localized-multiline-text-input): add support for isCondensed pro… #2793

feat(localized-multiline-text-input): add support for isCondensed pro… #2793

Conversation

Sarah4VT commented Apr 23, 2024 • edited Loading

Summary

Description

changeset-bot bot commented Apr 23, 2024 • edited Loading

🦋 Changeset detected

vercel bot commented Apr 23, 2024 • edited Loading

Sarah4VT commented Apr 23, 2024 • edited Loading

kark commented Apr 24, 2024

chloe0592 commented Apr 24, 2024

ddouglasz commented Apr 24, 2024

Sarah4VT commented Apr 24, 2024

ddouglasz left a comment

Choose a reason for hiding this comment

CarlosCortizasCT commented Apr 24, 2024 • edited Loading

Sarah4VT commented Apr 24, 2024

ddouglasz left a comment

Choose a reason for hiding this comment

ddouglasz Apr 25, 2024

Choose a reason for hiding this comment

ddouglasz Apr 25, 2024

Choose a reason for hiding this comment

ddouglasz Apr 25, 2024

Choose a reason for hiding this comment

ddouglasz Apr 25, 2024

Choose a reason for hiding this comment

CarlosCortizasCT commented Apr 25, 2024 • edited Loading

kterry1 left a comment

Choose a reason for hiding this comment

Sarah4VT commented Apr 25, 2024

Sarah4VT commented Apr 25, 2024

CarlosCortizasCT commented Apr 25, 2024

Sarah4VT Apr 25, 2024

Choose a reason for hiding this comment

CarlosCortizasCT Apr 26, 2024

Choose a reason for hiding this comment

Sarah4VT commented Apr 25, 2024

FilPob commented Apr 26, 2024

CarlosCortizasCT commented Apr 26, 2024

FilPob commented Apr 26, 2024

Sarah4VT commented Apr 26, 2024

FilPob commented Apr 26, 2024

CarlosCortizasCT left a comment

Choose a reason for hiding this comment

Sarah4VT commented Apr 23, 2024 •

edited

Loading

changeset-bot bot commented Apr 23, 2024 •

edited

Loading

vercel bot commented Apr 23, 2024 •

edited

Loading

Sarah4VT commented Apr 23, 2024 •

edited

Loading

CarlosCortizasCT commented Apr 24, 2024 •

edited

Loading

CarlosCortizasCT commented Apr 25, 2024 •

edited

Loading