Skip to content

Conversation

@dcalhoun
Copy link
Member

@dcalhoun dcalhoun commented Oct 30, 2025

Tip

I recommend reviewing each commit individually to simplify code review.

Important

#45715 builds upon this, so any manual testing should be performed on that branch.

Refactor existing code to use appropriate string methods, improve organization, and ensure restored global state. The majority of the changes are relocating existing code. The only new code is a try/final block and string utility usage.

Proposed changes:

  • Prefer str_contains and str_starts_with over strpos.
  • Reduce get_items() complexity by extracting disparate functions.
  • Wrap core logic with try/final to ensure global state restoration.

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

N/A

Does this pull request change what data or activity we track or use?

No

Testing instructions:

  • Verify existing automated tests pass.
  • Smoke test the endpoint by submitting requests via the API Console or curl.

Simplify existing logic with helpful utilities.
Extract various work to simplify the primary function.
@dcalhoun dcalhoun added [Status] In Progress [Type] Janitorial [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ labels Oct 30, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Oct 30, 2025

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the refactor/improve-editor-assets-endpoint branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack refactor/improve-editor-assets-endpoint

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@github-actions
Copy link
Contributor

github-actions bot commented Oct 30, 2025

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!


Jetpack plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

@jp-launch-control
Copy link

Code Coverage Summary

Coverage changed in 1 file.

File Coverage Δ% Δ Uncovered
projects/plugins/jetpack/_inc/lib/core-api/wpcom-endpoints/class-wpcom-rest-api-v2-endpoint-block-editor-assets.php 179/189 (94.71%) 0.56% 0 💚

Full summary · PHP report · JS report

array_keys( WP_Block_Type_Registry::get_instance()->get_all_registered() ),
function ( $block_name ) {
return strpos( $block_name, 'core/' ) === 0;
return str_starts_with( $block_name, 'core/' );
Copy link
Member Author

Choose a reason for hiding this comment

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

This and similar changes merely change generic string utilities to more explicit ones to better communicate intent.

Comment on lines +228 to +232
} finally {
// Always restore original asset state, even if an exception occurred
$wp_styles = $current_wp_styles;
$wp_scripts = $current_wp_scripts;
}
Copy link
Member Author

Choose a reason for hiding this comment

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

This try/finally block as added to ensure global state is restored in the event of an error. It will likely have no impact, but felt worthwhile nonetheless.

Copy link
Member Author

Choose a reason for hiding this comment

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

These changes solely relocate existing code, aside from the inline comments noting otherwise.

Copy link

@kean kean left a comment

Choose a reason for hiding this comment

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

LGTM

@dcalhoun dcalhoun added [Status] Ready to Merge Go ahead, you can push that green button! and removed [Status] In Progress labels Nov 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Status] Ready to Merge Go ahead, you can push that green button! [Type] Janitorial

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants