-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Site Editor: Remove unused 'useSiteEditorSettings' hook #64892
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: -38 B (0%) Total Size: 1.77 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Smoke tested branch. Site editor still works :)
) Co-authored-by: Mamaduka <[email protected]> Co-authored-by: ramonjd <[email protected]>
Cool :) |
This largely reverts #24, which resulted in several regressions. Namely, oddities in the block toolbar emptying and empty Patterns/Media tabs in the block inserter. The previous changes was implemented to workaround an experimental API that is no longer exported after WordPress/gutenberg#64892. That remains an issue, but the new workaround is to patch Gutenberg itself to export this necessary API with `patch-package`.
This largely reverts #24, which resulted in several regressions. Namely, oddities in the block toolbar emptying and empty Patterns/Media tabs in the block inserter. The previous changes was implemented to workaround an experimental API that is no longer exported after WordPress/gutenberg#64892. That remains an issue, but the new workaround is to patch Gutenberg itself to export this necessary API with `patch-package`.
This largely reverts #24, which resulted in several regressions. Namely, oddities in the block toolbar emptying and empty Patterns/Media tabs in the block inserter. The previous changes was implemented to workaround an experimental API that is no longer exported after WordPress/gutenberg#64892. That remains an issue, but the new workaround is to patch Gutenberg itself to export this necessary API with `patch-package`.
This largely reverts #24, which resulted in several regressions. Namely, oddities in the block toolbar emptying and empty Patterns/Media tabs in the block inserter. The previous changes was implemented to workaround an experimental API that is no longer exported after WordPress/gutenberg#64892. That remains an issue, but the new workaround is to patch Gutenberg itself to export this necessary API with `patch-package`.
This largely reverts #24, which resulted in several regressions. Namely, oddities in the block toolbar emptying and empty Patterns/Media tabs in the block inserter. The previous changes was implemented to workaround an experimental API that is no longer exported after WordPress/gutenberg#64892. That remains an issue, but the new workaround is to patch Gutenberg itself to export this necessary API with `patch-package`.
* build: Add patch-package * build: Configure patch-package * fix: Replace unsupported editor architecture This largely reverts #24, which resulted in several regressions. Namely, oddities in the block toolbar emptying and empty Patterns/Media tabs in the block inserter. The previous changes was implemented to workaround an experimental API that is no longer exported after WordPress/gutenberg#64892. That remains an issue, but the new workaround is to patch Gutenberg itself to export this necessary API with `patch-package`. * fix: Disable interception `blob:` URLs leading to an Android crash While the reason for why the `blob:` requests trigger is unknown, they originate when utilizing the block inserter's Patterns tab. The requests seemingly originate from the embedded editor previews rendered for each pattern.
What?
PR removes the unused
useSiteEditorSettings
hook from thecore/edit-site
package. I've also removeduseBlockEditorSettings
exported as private API.Why?
The hook hasn't been used since #62146.
Testing Instructions
CI checks should be green.
Testing Instructions for Keyboard
Same.