wenchun / jsdoc-toolkit

Automatically exported from code.google.com/p/jsdoc-toolkit
0 stars 0 forks source link

2.0 beta not picking up all @name'd functions #113

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Docs created for withjs.js miss glow.widgets.Overlay#additionalMethod (line 75)

widthoutjs.js contains the same documentation but with all javascript
removed, when building docs on this file jsdoc-toolkit returns the error:
oops: undefined
undefined

Is there an option to force jsdoc-toolkit to ignore all javascript and
build docs purely from the metadata in comments?

Not using -a, using jsdoc template.
WinXP
jsdoc-toolkit 2.0 beta
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)

Original issue reported on code.google.com by jaffathe...@gmail.com on 27 Mar 2008 at 12:09

Attachments:

GoogleCodeExporter commented 8 years ago
I am in the process of resolving the root of this problem, but I agree a flag to
ignore source code would make things go faster and more reliably when you only 
want
the comments parsed. That will likely be a -i flag in the next release.

Original comment by micmath on 28 Mar 2008 at 2:02

GoogleCodeExporter commented 8 years ago
Support for the -n or --nocode option was committed in revision 556. This will
additionally become a meta tag in a future release to allow you to make code
invisible in specific sections of files.

/**#nocode+*/
    //code is not seen in here but doc comments are
/**#nocode-*/

Original comment by micmath on 1 Apr 2008 at 12:31