Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find out what "nocompile" and "nodoc" annotation mean? #81

Open
adam-singer opened this issue Oct 23, 2013 · 3 comments
Open

Find out what "nocompile" and "nodoc" annotation mean? #81

adam-singer opened this issue Oct 23, 2013 · 3 comments

Comments

@adam-singer
Copy link
Member

Anything with a nocompile and nodoc should be removed from the idl model/transformation part to the chrome model. @devoncarew do you know who we could confirm this with?

app_window.idl:

[nocompile, nodoc] static void initializeAppWindow(object state);
@devoncarew
Copy link
Contributor

nodoc I'm certain means "don't generate API docs for this for http://developer.chrome.com/apps/api_index.html"

nocompile I don't know about. Some indication to the C++ backend? @srsaroop

I'll ask around -

@devoncarew
Copy link
Contributor

A bit more info: nodoc is also used to deprecate an API. So, the method still exists and can be called, but no documentation is generated for it, so its hard to discover.

@adam-singer
Copy link
Member Author

@devoncarew any update on nocompile ? Going to add an issue on the new project to implement nodoc as a @deprecated annotation in the generated dart code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants