Query for supported properties, for a supported post-type #33
Comments
|
Or as suggested by @manton off the back of this #8 (comment) |
|
I've implemented a version of this in Micro.blog to see how it would look. It returns the supported properties directly from |
|
Looks good, @manton. I'm wondering about making some distinction between required/optional properties, as I'll have different handling for them internally, and it may be good for the client to be able to provide some feedback to the user if they're not provided. What do you think? |
|
Personally I'm having trouble seeing where required properties would be needed. As an example, technically |
|
I have implemented this, and have added the {
"syndicate-to": [
...
],
"media-endpoint": "https://www-api.jvt.me/micropub/media",
"q": [
"post-types",
...
],
"post-types": [
{
"type": "bookmark",
"name": "Bookmark",
"properties": [
"bookmark-of",
"name",
"published",
"category",
"content",
"syndication"
],
"required-properties": [
"bookmark-of",
"name",
"published"
]
},
{
"type": "like",
"name": "Like",
"properties": [
"like-of",
"published",
"category",
"content",
"name",
"syndication"
],
"required-properties": [
"like-of",
"published"
]
},
{
"type": "reply",
"name": "Reply",
"properties": [
"content",
"in-reply-to",
"published",
"category",
"name",
"photo",
"syndication"
],
"required-properties": [
"content",
"in-reply-to",
"published"
]
},
{
"type": "repost",
"name": "Repost",
"properties": [
"published",
"repost-of",
"content",
"category",
"syndication"
],
"required-properties": [
"published",
"repost-of"
]
},
{
"type": "rsvp",
"name": "RSVP",
"properties": [
"in-reply-to",
"published",
"rsvp",
"category",
"content",
"syndication"
],
"required-properties": [
"in-reply-to",
"published",
"rsvp"
]
},
{
"type": "note",
"name": "Note",
"properties": [
"content",
"published",
"category",
"syndication"
],
"required-properties": [
"content",
"published"
]
},
{
"type": "photo",
"name": "Photo",
"properties": [
"photo",
"published",
"category",
"content",
"syndication"
],
"required-properties": [
"photo",
"published"
]
},
{
"type": "step",
"name": "Step Counts",
"properties": [
"unit",
"num",
"start",
"end"
],
"required-properties": [
"unit",
"num",
"start",
"end"
]
},
{
"type": "event",
"name": "Event",
"properties": [
"end",
"name",
"published",
"start",
"content",
"url"
],
"required-properties": [
"end",
"name",
"published",
"start"
]
},
{
"type": "contact",
"name": "Contact",
"properties": [
"name",
"nickname",
"url",
"rel=twitter"
],
"required-properties": [
"name",
"nickname",
"url"
]
}
]
} |
|
I have updated my implementation to also expose an {
"type": "bookmark",
"name": "Bookmark",
"h": "entry",
"properties": [
"bookmark-of",
"name",
"published",
"category",
"content",
"syndication"
],
"required-properties": [
"bookmark-of",
"name",
"published"
]
} |
|
@jamietanna I'm working on supporting this with Micropublish, including In your example above I wanted to query how you treat syndication. I have |
|
That's a good point - it's not one I'd considered. It's also uncovered a bug (or maybe a feature 🤷🏽♂️) where sending (Originally published at: https://www.jvt.me/mf2/2020/10/lqei3/) |
|
Just reviewing this, it seems like it is close to being considered a stable extension. Maybe there aren't 3 clients yet, though? |
|
Hm, not yet. My website works as a Micropub client but I don't know if that actually counts here. |
As per my comment on #1, I would like an extension to configuration queries that would allow me to discover which properties are supported for a post-type.
My proposal from #1 (comment) is to perform i.e.
GET /q=post-types&post-type=note.This would support Query for Supported Properties syntax, but be specific to the given post-type we want to interrogate.
The text was updated successfully, but these errors were encountered: