Change Details

A config or modify action (not reset) includes the parameters of the applied protection, but the expiry isn't in a meaningful format. See, e.g., https://en.wikipedia.org/w/api.php?action=query&format=json&list=logevents&titles=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&formatversion=2&leprop=type%7Ctimestamp%7Cdetails&letype=stable&letitle=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&lelimit=10 ``` "logevents": [ { "params": { "override": 1, "autoreview": "autoconfirmed", "expiry": "20201101171850" }, "type": "stable", "action": "config", "timestamp": "2020-11-01T17:08:50Z" }, ``` The `timestamp` is nice but `params.expiry` is awful. It should be ISO-8601 like the `timestamp`. Other, core logevents details do this properly (e.g. [[ https://en.wikipedia.org/w/api.php?action=query&format=json&list=logevents&titles=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&formatversion=2&leprop=type%7Ctimestamp%7Cdetails&letype=protect&letitle=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&lelimit=10 | protect ]], [[ https://en.wikipedia.org/w/api.php?action=query&format=json&list=logevents&titles=User%3AThisIsaTest&formatversion=2&leprop=type%7Ctimestamp%7Cdetails&letype=block&letitle=User%3AThisIsaTest&lelimit=10 | block ]])

A config or modify action (not reset) includes the parameters of the applied protection, but the expiry isn't in a meaningful format as far as JavaScript is concerned. See, e.g., https://en.wikipedia.org/w/api.php?action=query&format=json&list=logevents&titles=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&formatversion=2&leprop=type%7Ctimestamp%7Cdetails&letype=stable&letitle=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&lelimit=10 ``` "logevents": [ { "params": { "override": 1, "autoreview": "autoconfirmed", "expiry": "20201101171850" }, "type": "stable", "action": "config", "timestamp": "2020-11-01T17:08:50Z" }, ``` The `timestamp` is nice but `params.expiry` is awful. It should be ISO-8601(ish) like the `timestamp` and other core queries (e.g., other logevents details do this properly (e.g. [[ https://en.wikipedia.org/w/api.php?action=query&format=json&list=logevents&titles=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&formatversion=2&leprop=type%7Ctimestamp%7Cdetails&letype=protect&letitle=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&lelimit=10 | protect ]], [[ https://en.wikipedia.org/w/api.php?action=query&format=json&list=logevents&titles=User%3AThisIsaTest&formatversion=2&leprop=type%7Ctimestamp%7Cdetails&letype=block&letitle=User%3AThisIsaTest&lelimit=10 | block ]])).

A config or modify action (not reset) includes the parameters of the applied protection, but the expiry isn't in a meaningful format as far as JavaScript is concerned. See, e.g., https://en.wikipedia.org/w/api.php?action=query&format=json&list=logevents&titles=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&formatversion=2&leprop=type%7Ctimestamp%7Cdetails&letype=stable&letitle=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&lelimit=10 ``` "logevents": [ { "params": { "override": 1, "autoreview": "autoconfirmed", "expiry": "20201101171850" }, "type": "stable", "action": "config", "timestamp": "2020-11-01T17:08:50Z" }, ``` The `timestamp` is nice but `params.expiry` is awful. It should be ISO-8601(ish) like the `timestamp`. Other and other core queries (e.g., coreother logevents details do this properly (e.g. [[ https://en.wikipedia.org/w/api.php?action=query&format=json&list=logevents&titles=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&formatversion=2&leprop=type%7Ctimestamp%7Cdetails&letype=protect&letitle=Wikipedia%3AAdministrators'%20guide%2FProtecting%2FProtect&lelimit=10 | protect ]], [[ https://en.wikipedia.org/w/api.php?action=query&format=json&list=logevents&titles=User%3AThisIsaTest&formatversion=2&leprop=type%7Ctimestamp%7Cdetails&letype=block&letitle=User%3AThisIsaTest&lelimit=10 | block ]])).