Update: Add medium_large size for wp_prepare_attachment_for_js()

[Debarghya-Banerjee]

Trac Ticket: Core-43413

Overview

• This pull request introduces the addition of the medium_large image size to the wp_prepare_attachment_for_js function in WordPress. This enhancement allows for better handling and retrieval of the medium_large image size in the JavaScript context, providing developers with more flexibility when working with media attachments.

Changes Made

• Modified the wp_prepare_attachment_for_js function to include the medium_large image size.
  Ensured that the new size is appropriately registered and available for use in the media library.

Benefits

• Improved Media Management: By including the medium_large size, users can more effectively manage and display images without needing to generate additional sizes manually.

• Better Performance: Utilizing the appropriate image size can improve page load times and overall performance, particularly on responsive designs where image dimensions are critical.

[github-actions]

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 props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props debarghyabanerjee.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.