-
Notifications
You must be signed in to change notification settings - Fork 58
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
Add support for Story block rendering (part 3): rename refactor #2706
Add support for Story block rendering (part 3): rename refactor #2706
Conversation
Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job! |
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.
Approved via Automattic/jetpack#17456 (review) and WordPress/gutenberg#26005 (review)
Since this CI error also happens on the target branch, let's merge and solve the issue on the target branch itself 👍
This PR contains needed work to rename component to
BlockMediaUpdateProgress
(see Automattic/jetpack#17456)Related PRs:
Gutenberg: WordPress/gutenberg#26005
Jetpack: Automattic/jetpack#17456
WPAndroid: wordpress-mobile/WordPress-Android#13101
To test:
These changes aim at having a more generalized naming of methods that allow them to signify they are indeed reusable.
Given the Story block intrinsically is a collection of files represented by an object array named
mediaFiles
,we're giving collectively these names to the related method, for exampleonStoryCreatorRequestListener
has been renamed toonMediaFilesEditorLoadRequestListener
, given from Gutenberg the mediaFiles array gets passed on so it can be modified externally and then be replaced back once done editing.PR submission checklist: