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.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: yashjawale <yashjawale@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>
Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Co-authored-by: joemcgill <joemcgill@git.wordpress.org>

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

Updated ✅

I've looked into it a bit more, but would simply specifying all as the status solve the problem? The WP_Comment_Query class allows all as the status, and adds a condition for comments with a status of approved or hold. all might also be available in the REST API.

https://github.com/WordPress/wordpress-develop/blob/7289643a4d6a901a04f13b0359c95a1df5af63d3/src/wp-includes/class-wp-comment-query.php#L571-L574

Woah! I wasn't aware of this, might just do the trick 🚀

Perhaps the status values should be specified in documentation, currently it just says that the query's default value is approve

all status value appears to work, Thanks!
Updated ✅

I've looked into it a bit more, but would simply specifying all as the status solve the problem? The WP_Comment_Query class allows all as the status

Yes! Good point - 'all' will work for now. That said, I still feel we should add the multi-status support to the end point. The underlying comments class already supports arrays for the status field so the REST API lacking support is probably a bug/oversight. We may need more fine grained views of comments later where this could be useful.

I still feel we should add the multi-status support to the end point.

I agree, the block commenting might require additional comment status in the feature. That said, can we merge this PR for now?

That said, can we merge this PR for now?

Sure. This isn't a blocker.

OK, it seems to be ready to ship.

@WordPress/gutenberg-design, I believe this PR accurately implements the design proposed here, but if you have any design feedback, please leave a comment and we'll address it in a follow-up.