discard REST endpoint
Discard a saved editing draft using the current state checks.
Endpoint#
Discard a saved editing draft using the current state checks.
/wp-json/cantata-edit/v1/discard
Named regular-expression groups in this registered route are path parameters. Replace them with an actual matching value when constructing a request.
POST#
This operation uses a server permission callback. Browser clients need an authenticated WordPress session and REST nonce. The server checks the relevant caller capability and feature gates.
Permission expression in this release:
'permission_callback' => static fn( $req ) => current_user_can( 'edit_post', (int) $req['post_id'] ),
Registered argument schema#
{
"post_id": {
"type": "integer",
"required": true
},
"parts": {
"type": "boolean",
"default": false
},
"base": {
"type": "object",
"default": []
},
"force": {
"type": "boolean",
"default": false
}
}
WordPress applies these registered field rules before the callback. Feature-specific validation can add further constraints.
Callback input keys#
base, force, parts, post_id. This literal-key inventory supplements the registered schema; nested objects and downstream validators can define additional structure.
Implementation#
- cantata_edit_rest_discard
- cantata_edit_atomic
- cantata_edit_drop_meta
- cantata_edit_page_rev
- cantata_edit_part_draft_key
Client handling#
Use HTTPS on production sites. Treat authentication failures, validation errors, missing records, and stale-revision conflicts as different outcomes. Read the returned WordPress error code and message. Before retrying a timed-out mutation, determine whether the first request succeeded. Prefer the documented higher-level editor or Ability workflow when an endpoint coordinates several metadata owners.