On Fri, Jan 29, 2016 at 1:41 PM, Bináris wikiposta@gmail.com wrote:
2016-01-29 18:56 GMT+01:00 Brad Jorsch (Anomie) bjorsch@wikimedia.org:
by going to https://www.mediawiki.org/wiki/Special:ApiFeatureUsage, entering your agent (or any useful prefix of it), and looking for "https-expected".
What does *unclear-"now"-timestamp* mean here?
For various API timestamp-typed parameters, you can pass unusual values such as the empty string or "0" and it will be interpreted as meaning "now", which doesn't make very much sense except for the fact that it has always done that. If you really mean "now", you should pass that as the value instead.
action=edit even has to hack around this to avoid spurious edit conflicts if you do it for the 'basetimestamp' parameter. Ideally we'd make empty string and '0' be rejected as invalid timestamps, but first people have to stop passing them in.
2016-01-29 20:06 GMT+01:00 Brad Jorsch (Anomie) bjorsch@wikimedia.org:
On Fri, Jan 29, 2016 at 1:41 PM, Bináris wikiposta@gmail.com wrote:
2016-01-29 18:56 GMT+01:00 Brad Jorsch (Anomie) bjorsch@wikimedia.org:
by going to https://www.mediawiki.org/wiki/Special:ApiFeatureUsage, entering your agent (or any useful prefix of it), and looking for "https-expected".
What does *unclear-"now"-timestamp* mean here?
For various API timestamp-typed parameters, you can pass unusual values such as the empty string or "0" and it will be interpreted as meaning "now", which doesn't make very much sense except for the fact that it has always done that. If you really mean "now", you should pass that as the value instead.
action=edit even has to hack around this to avoid spurious edit conflicts if you do it for the 'basetimestamp' parameter. Ideally we'd make empty string and '0' be rejected as invalid timestamps, but first people have to stop passing them in.
Thank you! I know it's from Pywikibot because that was the string I entered. :-)
wikitech-l@lists.wikimedia.org