Skip to content

Script Loader: Trigger _doing_it_wrong() when wp_set_script_translations() is called before script registration#12475

Open
shrivastavanolo wants to merge 1 commit into
WordPress:trunkfrom
shrivastavanolo:fix/script-translations-doing-it-wrong
Open

Script Loader: Trigger _doing_it_wrong() when wp_set_script_translations() is called before script registration#12475
shrivastavanolo wants to merge 1 commit into
WordPress:trunkfrom
shrivastavanolo:fix/script-translations-doing-it-wrong

Conversation

@shrivastavanolo

Copy link
Copy Markdown

This PR updates wp_set_script_translations() to trigger _doing_it_wrong() when it is called for a script that has not yet been registered.

Previously, the function silently failed because WP_Scripts::set_translations() returned false, making it difficult for developers to identify incorrect usage.

Trac ticket: https://core.trac.wordpress.org/ticket/50749

Use of AI Tools

AI assistance: Yes
Tool(s): ChatGPT
Model(s): GPT-5.1
Used for: Initial code skeleton; final implementation was edited by me.


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@github-actions

Copy link
Copy Markdown

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 shreya0shrivastava.

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

@github-actions

Copy link
Copy Markdown

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

  • 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant