Open manton opened 4 years ago
Edited to remove speculation about post-types
. They are not really the same thing as the type
for JSON requests.
I'm a bit hesistant about q=source
being q=items
because of the semantics of the query. q=config
is a bit weird because it's very variable depending on what extensions you've defined (maybe could be solved/normalized with #44).
That said, would normalizing the output for q=contact
, q=category
, q=source
and q=syndicate-to
to be something similar to what q=source
gives? Namely, assuming a items
and paging
being provided at the least for queries that are meant to return a list of zero or more items.
Documenting a few differences that came up in chat. I'm not necessarily suggesting any of this change, because a lot of these have been implemented for a while. But there should probably be a kind of "style guide" for new extensions.
q=contact:
q=contacts
.q=category:
contact
, but probably reads better asq=categories
too.q=source (without a
url
param):q=source
from the original spec, could beq=items
.q=config:
media-endpoint
, also returns adestination
array if the user has multiple sites configured. I personally like including some of these things inq=config
because it's easy to get them in one call, but probably should be a pluraldestinations
array in the response.post-types
array.q=syndicate-to:
q=config
returns asyndicate-to
array. This is in the original Micropub spec.