[wp-trac] [WordPress Trac] #35658: Provide additional data for registered meta through register_meta()

[WordPress Trac]

#35658: Provide additional data for registered meta through register_meta()
-------------------------------------------------+-------------------------
 Reporter:  jeremyfelt                           |       Owner:  helen
     Type:  task (blessed)                       |      Status:  accepted
 Priority:  high                                 |   Milestone:  4.6
Component:  Options, Meta APIs                   |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-unit-tests needs-testing has-  |     Focuses:
  patch rest-api needs-dev-note                  |
-------------------------------------------------+-------------------------

Comment (by jeremyfelt):

 Any `WP_Curie` class should be handled in another ticket. We aren't going
 that far down the path as part of this solution, even if we do stick with
 colon delimited strings.

 Separately from the CURIE discussion, feedback is needed on this:

 Replying to [comment:127 jeremyfelt]:
 > In another approach, the onus is on the developer to choose a unique key
 name, especially for private data. This would allow us to skip all of the
 subtype handling and just start handling registered meta without adjusting
 filters or the function signatures of many `_meta*()` functions.
 >
 > Thoughts?

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