From bb662f909bb77ea2aad8fd3fde467cae61bd2d02 Mon Sep 17 00:00:00 2001 From: Fomafix Date: Tue, 29 Sep 2015 16:09:47 +0000 Subject: [PATCH] mediawiki.messagePoster: Update comments after mw.Api file renames * Use class name instead of file name * Expand abbreviation Follow-up 0bfdd927 Change-Id: I33ad2b10ffb4b4e5e3a38a5c6f644eb183134a36 --- .../mediawiki.messagePoster.WikitextMessagePoster.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/resources/src/mediawiki.messagePoster/mediawiki.messagePoster.WikitextMessagePoster.js b/resources/src/mediawiki.messagePoster/mediawiki.messagePoster.WikitextMessagePoster.js index 296576b4df..ad01865620 100644 --- a/resources/src/mediawiki.messagePoster/mediawiki.messagePoster.WikitextMessagePoster.js +++ b/resources/src/mediawiki.messagePoster/mediawiki.messagePoster.WikitextMessagePoster.js @@ -39,7 +39,7 @@ if ( resp.edit.result === 'Success' ) { return $.Deferred().resolve( resp, jqXHR ); } else { - // mediawiki.api.js checks for resp.error. Are there actually cases where the + // mw.Api checks for response error. Are there actually cases where the // request fails, but it's not caught there? return $.Deferred().reject( 'api-unexpected' ); } -- 2.20.1