Skip to content

Conversation

@katinthehatsite
Copy link
Contributor

Related issues

We have last updated this dependency over 6 months ago and now with the renewed focus on core components, it would be good to have the most recent updates and states of all the components in Studio. Additionally, I noticed that there were some fixes added in the new version for the Guide component that would allow us to remove some code that we added on our end (for example https://github.com/WordPress/gutenberg/pull/65680/files)

Proposed Changes

I propose to update wordpress/components dependency.

Testing Instructions

  • Pull the changes from this branch
  • Start the app with npm install && npm start
  • Holistically check that the app works (open different modals, settings etc.)
  • Observe that there are no warnings in the dev console

Pre-merge Checklist

  • Have you checked for TypeScript, React or other console errors?

@katinthehatsite katinthehatsite self-assigned this Apr 11, 2025
@katinthehatsite katinthehatsite requested a review from a team April 11, 2025 10:58
Copy link
Contributor

@gcsecsey gcsecsey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested the app and it holistically works as expected after the changes.

I did notice a new warning in the dev console after doing these steps:

  • Open the What's New modal from the Help menu, and walk over the screens
  • Walk through the tabs of a site
  • Try to update a preview site's name

CleanShot 2025-04-11 at 13 17 46@2x

Copy link
Contributor

@gcsecsey gcsecsey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did a clean install and launch on the same branch, and I can't reproduce the warning being thrown previously

After doing the same steps, I'm not getting any warnings or errors now:
CleanShot 2025-04-11 at 13 24 51@2x

@ivan-ottinger
Copy link
Contributor

Nice! That is great that the new version is fixing some of those issues.

Similarly to Gergely, I did not observe any issues in the UI, just some of the unit tests are failing.

@katinthehatsite
Copy link
Contributor Author

Similarly to Gergely, I did not observe any issues in the UI, just some of the unit tests are failing.

Nice, thanks. I will take a look at the tests but I will wait for Studio release first before merging this in any case

expect( useSnapshots().updateSnapshot ).not.toHaveBeenCalled();

// Wait for the modal to be fully closed after the exit animation
await waitFor( () => {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It took me a bit of time to figure out why the tests were failing here. It seems to be related to this PR: WordPress/gutenberg@4e7e9f7

It added some exit animation so we need to wait for the promises to resolve first

@katinthehatsite katinthehatsite merged commit fd3e5f3 into trunk Apr 14, 2025
8 checks passed
@katinthehatsite katinthehatsite deleted the update/wordpress-components-dependency branch April 14, 2025 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants