[wp-trac] [WordPress Trac] #48823: Collect all REST API meta errors at once

[WordPress Trac]

#48823: Collect all REST API meta errors at once
-------------------------------------------------+-------------------------
 Reporter:  TimothyBlynJacobs                    |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.4
Component:  REST API                             |     Version:  4.7
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-      |     Focuses:
  testing-info                                   |
-------------------------------------------------+-------------------------

Comment (by hellofromTonya):

 In discussing with @azaozz, we both have concerns of potential regressions
 and/or unexpected behaviors due to the code not bailing out immediately
 with an error, i.e. being allowed to continue processing.

 Given how important the REST API is, we're thinking this one is a good
 `early` candidate. Rather than committing it right before 6.4 Beta 1,
 instead commit it when 6.5 Alpha opens.

 [https://wordpress.slack.com/archives/C02RQBWTW/p1695674437369609 I
 noted]:
 >`early` would give it a long soak time to potentially discover if there
 are indeed regressions or unexpected behaviors. For example, the Gutenberg
 plugin uses the REST API. It's a good candidate to flush out if there are
 any unknown issues.

 @azaozz [https://wordpress.slack.com/archives/C02RQBWTW/p1695674541365039
 noted]:
 >Yea, thinking it may be a bit risky, and testing it and confirming it
 doesn't bring a regression would be great

 @TimothyBlynJacobs @spacedmonkey what do you both think? Are there risks?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48823#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform