[wp-trac] [WordPress Trac] #48401: Saving a Post Breaks in Gutenberg if you have a custom taxonomy named Status

[WordPress Trac]

#48401: Saving a Post Breaks in Gutenberg if you have a custom taxonomy named
Status
-------------------------------------------------+-------------------------
 Reporter:  kingkool68                           |       Owner:  fgiannar
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.4
Component:  REST API                             |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug needs-refresh has-    |     Focuses:
  unit-tests                                     |
-------------------------------------------------+-------------------------

Comment (by fgiannar):

 @TimothyBlynJacobs
 I guess we could keep an array of the taxonomy bases and check against it
 or keep a copy of the schema properties before starting the taxonomy loop,
 but I wouldn't like the idea of adding extra code outside the conditional
 check that produces the warning only for utilising it there...

 Technically the message is correct, since if the error is produced because
 of 2 taxonomies sharing a common rest_base, the first one is already
 defined as an existing schema property.

 Nevertheless, if you believe it's best to differentiate the warnings let
 me know and I will submit another patch.

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