You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This proposal is to specifically amend the specification to include the following extensions related to any query made to the Micropub endpoint. Being as these touch multiple extensions, standardizing these would be preferable within the spec.
This would create a universal way to interact with any query, whether built into the spec or not. While many queries do not belong in the spec, but as extensions, I think these concepts would be better served by amending the specification.
The text was updated successfully, but these errors were encountered:
I think it's a good idea to add a general pagination section to the spec. However, I think the 1 and 2 above conflict with 3. I've been adding support for limit and offset but not the before/after-style pagination from Microsub.
To be clear, by "conflict" I just mean they are different ways to solve essentially the same thing. I think it would be confusing to recommend that both solutions are used. I don't have strong opinions about it except that I've already implemented limit/offset. It is kind of a bummer that it's not consistent with Microsub, but I think that's probably okay.
This proposal is to specifically amend the specification to include the following extensions related to any query made to the Micropub endpoint. Being as these touch multiple extensions, standardizing these would be preferable within the spec.
This would create a universal way to interact with any query, whether built into the spec or not. While many queries do not belong in the spec, but as extensions, I think these concepts would be better served by amending the specification.
The text was updated successfully, but these errors were encountered: