Lazily require types when validating Extensions API calls

chrome/common/extensions/api/content_settings.json

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 [
   {
     "namespace": "contentSettings",
     "types": [
       {
         "id": "ResourceIdentifier",
         "type": "object",
         "properties": {
           "id": {
             "type": "string",
             "description": "The resource identifier for the given content type."
           },
           "description": {
             "type": "string",
             "optional": true,
             "description": "A human readable description of the resource."
           }
         },
         "description": "The only content type using resource identifiers is $ref:contentSettings.plugins. For more information, see <a href=\"contentSettings.html#resource-identifiers\">Resource Identifiers</a>."
       },
       {
         "id": "ContentSetting",
+        "js_module": "ContentSetting",
         "type": "object",
         "functions": [
           {
             "name": "clear",
             "type": "function",
             "description": "Clear all content setting rules set by this extension.",
             "parameters": [
               {
                 "name": "details",
                 "type": "object",
@@ skipping 175 matching lines @@
         "$ref": "ContentSetting",
         "description": "Whether to allow sites to show desktop notifications. One of<br><var>allow</var>: Allow sites to show desktop notifications,<br><var>block</var>: Don't allow sites to show desktop notifications,<br><var>ask</var>: Ask when a site wants to show desktop notifications. <br>Default is <var>ask</var>.<br>The primary URL is the main-frame URL. The secondary URL is not used.",
         "value": [
           "notifications",
           {"type":"string", "enum": ["allow", "block", "ask"]}
         ]
       }
     }
   }
 ]