chore(json-update): update json and regen all code

etc/api/gmail/v1/gmail-api.json

@@ -1,11 +1,11 @@
 {
  "kind": "discovery#restDescription",
- "etag": "\"ye6orv2F-1npMW3u9suM3a7C5Bo/hFGSutIVQj0PQfQgMG3Y44JNJU0\"",
+ "etag": "\"ye6orv2F-1npMW3u9suM3a7C5Bo/rcmL92SXMKTyKvGjL_5VhC8zz9s\"",
  "discoveryVersion": "v1",
  "id": "gmail:v1",
  "name": "gmail",
  "version": "v1",
- "revision": "20150303",
+ "revision": "20150526",
  "title": "Gmail API",
  "description": "The Gmail REST API.",
  "ownerDomain": "google.com",
@@ -419,6 +419,11 @@
      "type": "string",
      "description": "The immutable ID of the message."
     },
+    "internalDate": {
+     "type": "string",
+     "description": "The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the Date header. However, for API-migrated mail, it can be configured by client to be based on the Date header.",
+     "format": "int64"
+    },
     "labelIds": {
      "type": "array",
      "description": "List of IDs of labels applied to this message.",
@@ -622,6 +627,53 @@
      "description": "A short part of the message text."
     }
    }
+  },
+  "WatchRequest": {
+   "id": "WatchRequest",
+   "type": "object",
+   "description": "Set up or update a new push notification watch on this user's mailbox.",
+   "properties": {
+    "labelFilterAction": {
+     "type": "string",
+     "description": "Filtering behavior of labelIds list specified.",
+     "enum": [
+      "exclude",
+      "include"
+     ],
+     "enumDescriptions": [
+      "",
+      ""
+     ]
+    },
+    "labelIds": {
+     "type": "array",
+     "description": "List of label_ids to restrict notifications about. By default, if unspecified, all changes are pushed out. If specified then dictates which labels are required for a push notification to be generated.",
+     "items": {
+      "type": "string"
+     }
+    },
+    "topicName": {
+     "type": "string",
+     "description": "A fully qualified Google Cloud Pub/Sub API topic name to publish the events to. This topic name **must** already exist in Cloud Pub/Sub and you **must** have already granted gmail \"publish\" permission on it. For example, \"projects/my-project-identifier/topics/my-topic-name\" (using the new Cloud Pub/Sub \"v1beta2\" topic naming format).\n\nNote that the \"my-project-identifier\" portion must exactly match your Google developer project id (the one executing this watch request)."
+    }
+   }
+  },
+  "WatchResponse": {
+   "id": "WatchResponse",
+   "type": "object",
+   "description": "Push notification watch response.",
+   "properties": {
+    "expiration": {
+     "type": "string",
+     "description": "When Gmail will stop sending notifications for mailbox updates (epoch millis). Call watch again before this time to renew the watch.",
+     "format": "int64"
+    },
+    "historyId": {
+     "type": "string",
+     "description": "The ID of the mailbox's current history record.",
+     "format": "uint64"
+    }
+   }
   }
  },
  "resources": {
@@ -653,6 +705,58 @@
       "https://www.googleapis.com/auth/gmail.modify",
       "https://www.googleapis.com/auth/gmail.readonly"
      ]
+    },
+    "stop": {
+     "id": "gmail.users.stop",
+     "path": "{userId}/stop",
+     "httpMethod": "POST",
+     "description": "Stop receiving push notifications for the given user mailbox.",
+     "parameters": {
+      "userId": {
+       "type": "string",
+       "description": "The user's email address. The special value me can be used to indicate the authenticated user.",
+       "default": "me",
+       "required": true,
+       "location": "path"
+      }
+     },
+     "parameterOrder": [
+      "userId"
+     ],
+     "scopes": [
+      "https://mail.google.com/",
+      "https://www.googleapis.com/auth/gmail.modify",
+      "https://www.googleapis.com/auth/gmail.readonly"
+     ]
+    },
+    "watch": {
+     "id": "gmail.users.watch",
+     "path": "{userId}/watch",
+     "httpMethod": "POST",
+     "description": "Set up or update a push notification watch on the given user mailbox.",
+     "parameters": {
+      "userId": {
+       "type": "string",
+       "description": "The user's email address. The special value me can be used to indicate the authenticated user.",
+       "default": "me",
+       "required": true,
+       "location": "path"
+      }
+     },
+     "parameterOrder": [
+      "userId"
+     ],
+     "request": {
+      "$ref": "WatchRequest"
+     },
+     "response": {
+      "$ref": "WatchResponse"
+     },
+     "scopes": [
+      "https://mail.google.com/",
+      "https://www.googleapis.com/auth/gmail.modify",
+      "https://www.googleapis.com/auth/gmail.readonly"
+     ]
     }
    },
    "resources": {
@@ -953,7 +1057,7 @@
         },
         "startHistoryId": {
          "type": "string",
-         "description": "Required. Returns history records after the specified startHistoryId. The supplied startHistoryId should be obtained from the historyId of a message, thread, or previous list response. History IDs increase chronologically but are not contiguous with random gaps in between valid IDs. Supplying an invalid or out of date startHistoryId typically returns an HTTP 404 error code. A historyId is typically valid for at least a week, but in some circumstances may be valid for only a few hours. If you receive an HTTP 404 error response, your application should perform a full sync. If you receive no nextPageToken in the response, there are no updates to retrieve and you can store the returned historyId for a future request.",
+         "description": "Required. Returns history records after the specified startHistoryId. The supplied startHistoryId should be obtained from the historyId of a message, thread, or previous list response. History IDs increase chronologically but are not contiguous with random gaps in between valid IDs. Supplying an invalid or out of date startHistoryId typically returns an HTTP 404 error code. A historyId is typically valid for at least a week, but in some rare circumstances may be valid for only a few hours. If you receive an HTTP 404 error response, your application should perform a full sync. If you receive no nextPageToken in the response, there are no updates to retrieve and you can store the returned historyId for a future request.",
          "format": "uint64",
          "location": "query"
         },