Supporting more APIs with json_schema_compiler

chrome/common/extensions/api/cookies.json

 [
   {
     "namespace": "cookies",
+    "compile": true,

[not at google - send to devlin, 2012/02/05 23:42:12]

better be prepared to follow through with that :)

(or just revert for now)

actually, that makes me think, do we still need to set this property? the way
the build is set up at the moment is to list the appropriate scheme files in the
gyp; is that enough to know to compile it now?

(and then have a nocompile like there is a nodoc... I know you already had it
like this, but it seems more sensible, unless I'm missing something)

[calamity, 2012/02/06 11:51:18]

It's enough for now, but there's no facility for someone that wants to include
non-compiled types in the model.

I'll think about that but for now, removed.

     "types": [
       {
         "id": "Cookie",
         "type": "object",
         "description": "Represents information about an HTTP cookie.",
         "properties": {
           "name": {"type": "string", "description": "The name of the cookie."},
           "value": {"type": "string", "description": "The value of the cookie."},
           "domain": {"type": "string", "description": "The domain of the cookie (e.g. \"www.google.com\", \"example.com\")."},
           "hostOnly": {"type": "boolean", "description": "True if the cookie is a host-only cookie (i.e. a request's host must exactly match the domain of the cookie)."},
@@ skipping 172 matching lines @@
               "removed": {"type": "boolean", "description": "True if a cookie was removed."},
               "cookie": {"$ref": "Cookie", "description": "Information about the cookie that was set or removed."},
               "cause": {"min_version": "12.0.707.0", "type": "string", "enum": ["evicted", "expired", "explicit", "expired_overwrite", "overwrite"], "description": "The underlying reason behind the cookie's change. If a cookie was inserted, or removed via an explicit call to \"chrome.cookies.remove\", \"cause\" will be \"explicit\". If a cookie was automatically removed due to expiry, \"cause\" will be \"expired\". If a cookie was removed due to being overwritten with an already-expired expiration date, \"cause\" will be set to \"expired_overwrite\".  If a cookie was automatically removed due to garbage collection, \"cause\" will be \"evicted\".  If a cookie was automatically removed due to a \"set\" call that overwrote it, \"cause\" will be \"overwrite\". Plan your response accordingly."}
             }
           }
         ]
       }
     ]
   }
 ]