I still think that we should provide a simple API clients for JS, PHP, and
python. JS version should support both Browser node.js. The libs should
handle the most rudimentary API functioning like logins, warnings,
continuation, in the way that API devs feel is best, but nothing specific
to any
Is there a phab task for that.. ? :-)
On Mon, Apr 20, 2015 at 10:21 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
On Mon, Apr 20, 2015 at 1:19 PM, Jon Robson jdlrob...@gmail.com wrote:
I use mw.api so I suspect that to handle deprecation notices - does it
not? If not why not?
It would help to surface api deprecation notices into the JavaScript
console just like mw.deprecate does for more visibility.
I haven't got time to review every single API response for every
request mobile makes and I'm keen to help you be able to iterate on
the API quicker...
Jon
On Fri, Apr
I use mw.api so I suspect that to handle deprecation notices - does it
not? If not why not?
Basically I think these notices need to show up in php warning logs /
js console to get the attention they deserve.
On Mon, Apr 20, 2015 at 10:14 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
On
On Mon, Apr 20, 2015 at 12:57 PM, Jon Robson jdlrob...@gmail.com wrote:
It would help to surface api deprecation notices into the JavaScript
console just like mw.deprecate does for more visibility.
The API can and does already report deprecation warnings, and the way that
happens is on my
On Mon, Apr 20, 2015 at 1:19 PM, Jon Robson jdlrob...@gmail.com wrote:
I use mw.api so I suspect that to handle deprecation notices - does it
not? If not why not?
Because no one coded it for that framework yet?
--
Brad Jorsch (Anomie)
Software Engineer
Wikimedia Foundation
It doesn't seem like anyone's mentioned it yet, but it would be even nicer
IMHO to not even worry about this class of problems by versioning the API
itself. This way, you can provide an explicit upgrade path for
actively-developed clients while keeping old versions around for legacy
clients. As
On Mon, Apr 20, 2015 at 11:49 AM, Brian Gerstle bgers...@wikimedia.org wrote:
It doesn't seem like anyone's mentioned it yet, but it would be even nicer
IMHO to not even worry about this class of problems by versioning the API
itself. This way, you can provide an explicit upgrade path for
Previous announcement:
https://lists.wikimedia.org/pipermail/mediawiki-api-announce/2014-September/69.html
During the 1.25 development cycle, the API has been warning you if you're
specifying neither the continue nor rawcontinue parameters to
action=query. Recently this warning was targeted
