Add deprecation message in chrome.pushMessaging API

chrome/browser/extensions/api/push_messaging/push_messaging_api.cc

Index: chrome/browser/extensions/api/push_messaging/push_messaging_api.cc
diff --git a/chrome/browser/extensions/api/push_messaging/push_messaging_api.cc b/chrome/browser/extensions/api/push_messaging/push_messaging_api.cc
index c579e4473072de8ea4917edc04153f2cd443edcb..5c0a185f8099dbade98f6357d1696eeda0809fe7 100644
--- a/chrome/browser/extensions/api/push_messaging/push_messaging_api.cc
+++ b/chrome/browser/extensions/api/push_messaging/push_messaging_api.cc
@@ -48,7 +48,9 @@ const char kUserAccessTokenFailure[] =
 const char kAPINotAvailableForUser[] =
     "The API is not available for this user.";
 const int kObfuscatedGaiaIdTimeoutInDays = 30;
-}
+const char kDeprecationMessage[] =
+    "The chrome.pushMessaging API is deprecated. Use chrome.gcm API instead.";
+}  // namespace
 
 namespace glue = api::push_messaging;
 
@@ -94,6 +96,9 @@ PushMessagingGetChannelIdFunction::PushMessagingGetChannelIdFunction()
 PushMessagingGetChannelIdFunction::~PushMessagingGetChannelIdFunction() {}
 
 bool PushMessagingGetChannelIdFunction::RunAsync() {
+  // Issue a deprecation message.
+  WriteToConsole(content::CONSOLE_MESSAGE_LEVEL_WARNING, kDeprecationMessage);

[not at google - send to devlin, 2014/08/14 22:16:08]

How often do apps call this method? Because if it's being called often - for
whatever reason - it could get really spammy.

[fgorski, 2014/08/20 22:46:47]

I am seeing it used very rarely (2 other APIs).
app_window_api.cc:184 is actual deprecation message
alarms_api.cc:114 Not sure for what reason.

+

[not at google - send to devlin, 2014/08/14 22:16:08]

Also: we should add an install warning for when the permission is requested. I
can't remember where this is all done, yoz?

[Yoyo Zhou, 2014/08/15 01:40:13]

chrome_api_permissions?

I'm not sure I follow "install warning"... "when requested"

[not at google - send to devlin, 2014/08/15 15:54:17]

I mean the same warning that shows up if you request a permission that doesn't
exist, or append to InstallWarnings from a ManifestHandler. Is there an
idiomatic way to append arbitrary data to that?

[Yoyo Zhou, 2014/08/15 19:25:31]

I dunno, I would just try calling extension->AddInstallWarning.

Given that we have the error console, though, I don't know if adding the install
warning will help much additionally.

[fgorski, 2014/08/20 22:46:46]

We could add a check for deprecated permissions in ParseHelper in
permissions_parser.cc
    Feature::Availability availability =
        feature->IsAvailableToExtension(extension);
149:
    if (!availability.is_available()) {
      //stuff here (issues warning and removes permission)
      continue;
    }

    if (!availability.is_deprecated()) {
      extension->AddInstallWarning(
          InstallWarning(availability.message(), feature->name()));
    }

Of course that would require extension to Feature::Availability and adding a bit
to the manifest.

Ben do you think it is reasonable to do it now? Or can we spent some time and do
it right? I am sure it would be useful if we want to deprecate stuff in future.

[not at google - send to devlin, 2014/08/21 00:36:33]

I've wanted this actually, a feature file annotation to say an entire API is
deprecated (would be useful for the socket API as well, for example). What you
suggest sounds perfect.

   // Fetch the function arguments.
   scoped_ptr<glue::GetChannelId::Params> params(
       glue::GetChannelId::Params::Create(*args_));