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
A note on the Micropub spec highlights the ability to make a set of operations in one go to a Micropub server but not having the ability to get defined results. I'm proposing that we allow for another action for batch operations (like action=batch) that can take in a list of actions under the key "actions" that would be a list of objects mirroring the conventional body for the request for an update. This way, the client can define the order and the Micropub server can indicate at what action a failure occurred (and even consider rolling back, if it supports that).
A note on the Micropub spec highlights the ability to make a set of operations in one go to a Micropub server but not having the ability to get defined results. I'm proposing that we allow for another action for batch operations (like action=batch) that can take in a list of actions under the key "actions" that would be a list of objects mirroring the conventional body for the request for an update. This way, the client can define the order and the Micropub server can indicate at what action a failure occurred (and even consider rolling back, if it supports that).
(Originally published at: https://jacky.wtf/2022/12/5eRK)
The text was updated successfully, but these errors were encountered: