[wp-trac] [WordPress Trac] #35658: Provide additional data for registered meta through register_meta()
WordPress Trac
noreply at wordpress.org
Fri Jul 15 18:27:00 UTC 2016
#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 sc0ttkclark):
Replying to [comment:125 schlessera]:
> If you want to provide a class for CURIEs, you should definitely stick
to how the CURIE is officially defined. Otherwise, please don't call it a
CURIE, as that comes with a certain set of expectations.
>
> * The components are called `prefix` and `reference`
> * It should still work when you omit the `prefix` and leave the colon
I've changed terminology in my class to use prefix/reference. It already
worked if you didn't have a prefix (or reference) since it split by colon
during handling.
> * It should be possible to enclose it in brackets (this is called a
`SafeCURIE`).
I'm not sure we need SafeCURIE coverage just yet, since it's only used
when it's being used in context of a URI, and we haven't gotten there
(yet?).
RE: Felix, I'm not sure we are straying from the CURIE standard and
supporting multiple colon references separately, It's the prefix, and then
whatever comes after the colon will be treated as the reference for now.
Still open to further feedback.
https://gist.github.com/sc0ttkclark/1264c66297190548d138e785e39ab3d6
--
Ticket URL: <https://core.trac.wordpress.org/ticket/35658#comment:129>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list