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
Migrate edit-widgets store to thunks #35110
Conversation
Size Change: -309 B (0%) Total Size: 1.07 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.
The widget screen works as expected in my local tests.
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.
Code looks good 👍 Glad that we're throwing controls.js
in the bin. I didn't test this locally but if E2E tests pass then I'm happy since Kai did a pretty good job covering all the main widget flows.
I noticed we're missing doc comments for most of the export
ed actions that are being modified here. If you want bonus brownie points, maybe add these missing comments?
* @param {number} menuId Menu ID. | ||
* @return {Object} Action. | ||
*/ | ||
export function getNavigationPostForMenu( menuId ) { |
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.
How'd this get in here! 😛
Co-authored-by: George Mamadashvili <georgemamadashvili@gmail.com>
2a72b12
to
9a680d1
Compare
|
This PR migrates the edit-widgets data store to thunks, namely actions and resolvers. It also dependency on
@wordpress/data-controls
and on any other controls for that matter.How to test:
Open the widgets editor and confirm it loads and saves widgets as expected.