Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove isolated block editor #64097

Merged
merged 3 commits into from
May 27, 2022
Merged

Conversation

noahtallen
Copy link
Contributor

@noahtallen noahtallen commented May 27, 2022

Changes proposed in this Pull Request

The isolated block editor package has given us significant trouble with WordPress monorepo updates over the past several months. This time, it's completely blocking the release of Gutenberg to dotcom for an interesting chain of issues stemming from the removal of an experimental method in Gutenberg.

It's only used for an experiment @sarayourfriend did a year or two ago with Gutenberg in the Reader. We have no plans to actively continue work on that experiment, so it's fair to remove the code completely at this point. This lets us remove the isolated block editor package from our dependencies and that should unblock the gutenberg release.

Related discussion: p1653583842699789-slack-CBTN58FTJ

Testing instructions

  • In calypso.live, verify that comments in the Reader work properly.

Related to #64093

@github-actions
Copy link

github-actions bot commented May 27, 2022

@noahtallen noahtallen requested a review from a team May 27, 2022 00:29
@matticbot matticbot added the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label May 27, 2022
@noahtallen noahtallen self-assigned this May 27, 2022
@@ -42,6 +27,22 @@ logFilters:
level: discard
- pattern: "wp-calypso@workspace:. provides react-dom (pf5aa8) with version 17.0.2, which doesn't satisfy what @types/wordpress__block-editor and some of its descendants request"
level: discard
- pattern: "calypso@workspace:client provides react (pb0cb8) with version 17.0.2, which doesn't satisfy what @wordpress/block-editor and some of its descendants request"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

No clue why this is an issue now, but we can't get around it unless Gutenberg drops a transitive dependency.

Copy link
Contributor

@fullofcaffeine fullofcaffeine left a comment

Choose a reason for hiding this comment

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

LGTM!

@fullofcaffeine fullofcaffeine added the caused-by-gutenberg-upgrade Labels an issue (or PR) as caused by or related to a Gutenberg upgrade on WPCOM. label May 27, 2022
@fullofcaffeine fullofcaffeine merged commit f66e8ae into trunk May 27, 2022
@fullofcaffeine fullofcaffeine deleted the remove-isolated-block-editor branch May 27, 2022 00:42
@github-actions 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 May 27, 2022
@tyxla
Copy link
Member

tyxla commented Jun 5, 2022

Came late to this, but just wanted to say thanks for cleaning it up 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
caused-by-gutenberg-upgrade Labels an issue (or PR) as caused by or related to a Gutenberg upgrade on WPCOM.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants