-
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
Try having less of the tree within EditorProvider
#61874
Conversation
Size Change: -1 B (0%) Total Size: 1.74 MB
ℹ️ View Unchanged
|
Flaky tests detected in 16182fc. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/9195287608
|
EditorProvider
@@ -349,7 +342,16 @@ export default function Editor( { isLoading, onClick } ) { | |||
/> | |||
} | |||
content={ | |||
<> | |||
<EditorProvider |
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.
So I didn't dive yet into the issue to understand it properly but for me, conceptually at least, EditorProvider
should wrap the whole InterfaceSkeleton
, it provides the context for the canvas, the header and the sidebar. The fact that the header and sidebar continue to work with this change is just because we're doing the useSubRegistry={ false }
hack to allow third-party developers to access the core/editor store globally, without it, it would break both of these components as they won't be "talking" to the right store.
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.
Ok here's an alternative fix #61882
Closing in favor of #61882 🥳 |
What?
Trys a naive fix for some animations that are currently broken. It probably can generally make parts of the interface a teeny bit more snappy (less re-renders).
Why?
Fixes #60875 and fixes #61875.
How?
Moves
EditorProvider
to wrap less of the interface—just the content.Testing Instructions