Trac #65313: Extend WP_Comment_Query 'fields' to support individual c…#11935
Trac #65313: Extend WP_Comment_Query 'fields' to support individual c…#11935Anupkankale wants to merge 3 commits into
Conversation
…olumn names - Accepts a single valid column name (e.g. 'comment_post_ID') and returns a flat array of scalar values - Accepts an array of valid column names and returns stdClass objects per row - Invalid column names fall back to full WP_Comment objects - Existing 'ids' and '' (default) behaviour unchanged - Follows the same pattern as WP_User_Query Fixes https://core.trac.wordpress.org/ticket/65313
|
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. |
|
Thanks for the PR, but I'm closing in favor of #11934 since it lacks coding standards issues while also including unit tests. If you have any suggestions for that PR, please add them there. |
…olumn names
Fixes https://core.trac.wordpress.org/ticket/65313
Trac ticket:
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.