-
Notifications
You must be signed in to change notification settings - Fork 4
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
feature request: non-module docs should appear somewhere. #5
Comments
What do you mean by 'non-module' docs? I have run into problems trying to get some functions documented when they are inside a closure or specified in a way which dox has problems with. I think the way I worked around this is to make use of the |
I feel foolish. I actually implemented a A few nits remain:
Solution 1:
Solution 2:
I like that better, because it's more explicit. |
@module and @memberof together are enough to force a tree-like structure to the document. However @module requires a `ctx` object to get a sensible name (from ctx.name). For the `main` module (and in some other cases, like weird coding patters, evals, and anywhere else the regex pased detection in `dox` fails (Moz code like 'const','let', others), that name will be non-existent or wrong. Here: @module modname will specify a module name to use.
@module and @memberof together are enough to force a tree-like structure to the document. However @module requires a `ctx` object to get a sensible name (from ctx.name). For the `main` module (and in some other cases, like weird coding patters, evals, and anywhere else the regex pased detection in `dox` fails (Moz code like 'const','let', others), that name will be non-existent or wrong. Here: @module modname will specify a module name to use.
Even in Davis.js, the non-module functions don't appear in the docs.
The text was updated successfully, but these errors were encountered: