Add support for $ref'ing namespaces to server2.

Add support for $ref'ing namespaces to server2.


R=jyasskin@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=178029

[Jeffrey Yasskin, 2013-01-18 18:27:31]

https://codereview.chromium.org/12025022/diff/1/chrome/common/extensions/docs...
File chrome/common/extensions/docs/server2/reference_resolver.py (right):

https://codereview.chromium.org/12025022/diff/1/chrome/common/extensions/docs...
chrome/common/extensions/docs/server2/reference_resolver.py:71: if ref in
api_list:
Are the elements of api_list like "tabs" or "chrome.tabs"? Do you intend
$ref:tabs or $ref:chrome.tabs to work?

[not at google - send to devlin, 2013-01-18 18:30:25]

https://codereview.chromium.org/12025022/diff/1/chrome/common/extensions/docs...
File chrome/common/extensions/docs/server2/reference_resolver.py (right):

https://codereview.chromium.org/12025022/diff/1/chrome/common/extensions/docs...
chrome/common/extensions/docs/server2/reference_resolver.py:71: if ref in
api_list:
On 2013/01/18 18:27:31, Jeffrey Yasskin wrote:
> Are the elements of api_list like "tabs" or "chrome.tabs"? Do you intend
> $ref:tabs or $ref:chrome.tabs to work?

They're just like "tabs". There's no need for "chrome.tabs" to work.

Though I just realised that it may be better for this block to move below the
resolve-within-namespaces logic - say that the tabs API has a function called
windows. We probably want $ref:windows within the tabs API to resolve to the
windows function, not the windows namespace.

[Jeffrey Yasskin, 2013-01-18 22:02:34]

lgtm