Docs: Correct the $operator default for wp_filter_object_list() - #13245
Docs: Correct the $operator default for wp_filter_object_list()#13245itzmekhokan wants to merge 1 commit into
$operator default for wp_filter_object_list()#13245Conversation
The DocBlock documented the default as 'AND', but the function signature declares `$operator = 'and'`. Note that the value is case-insensitive, which is why the uppercase operator names and the lowercase default are both accurate. Fixes #65933.
|
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 Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe 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
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
wp_filter_object_list()documents its$operatordefault as'AND', but the function signature declares$operator = 'and'.The mismatch dates to the function's introduction in 3.0.0. Neither casing is wrong at runtime, since
WP_List_Util::filter()uppercases the operator before validating it, so the patch corrects the documented default to'and'and notes that the value is case-insensitive — the sentence that reconciles the uppercase operator names above it with the lowercase default.wp_list_filter()andWP_List_Util::filter()already document'AND'as both their default and their declared value, so they are left alone.Trac ticket: https://core.trac.wordpress.org/ticket/65933
Use of AI Tools
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.