Linking AvailabilityFinder with APIDataSource and intro-table templates.

chrome/common/extensions/api/types.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": "types",
-    "description": "The <code>chrome.types</code> API contains type declarations for Chrome. Currently, this comprises only a prototype for giving other APIs access to manage Chrome browser settings. This prototype is used, for example, for $ref:proxy.settings.",
+    "description": "The <code>chrome.types</code> API contains type declarations for Chrome. Currently, this comprises only a prototype for giving other APIs access to manage Chrome browser settings.",

[epeterson, 2013/07/03 19:05:02]

proxy.settings is linked to right after the intro-table... but also, the ref
wasn't interpreted when it was pulled from the JSON here.

[not at google - send to devlin, 2013/07/03 19:54:56]

Hm. It would be nice to make the $ref work, and probably not that much effort.

[epeterson, 2013/07/09 20:51:18]

Ok, I made the change in APIDataSource. It wasn't too difficult.

     "types": [
       {
         "id": "ChromeSetting",
         "type": "object",
         "js_module": "ChromeSetting",
         "customBindings": "ChromeSetting",
         "description": "An interface which allows access to a Chrome browser setting.",
         "functions": [
           {
             "name": "get",
@@ skipping 125 matching lines @@
                   }
                 }
               }
             ]
           }
         ]
       }
     ]
   }
 ]