You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
YUIDoc options have a (undocumented?) option nocode . That is set internally when the --no-code flag is used on the CLI.
When the option is set, the html version of the code files is NOT copied into the output directory. This is useful if you only want to publish the documentation and not the code.
The gulp-yuidoc copies generator copies the files property of the Parser data regardless of the nocode flag being set.
By adding a simple check we can ensure that the files are only generated if nocode is false. Something like..
And no code is generated for me. First parameter is parser configuration, second parameter is generator configuration, which takes nocode. But indeed, yuidoc is so lame on documentation....
YUIDoc options have a (undocumented?) option
nocode
. That is set internally when the--no-code
flag is used on the CLI.When the option is set, the html version of the code files is NOT copied into the output directory. This is useful if you only want to publish the documentation and not the code.
The gulp-yuidoc copies generator copies the
files
property of the Parser data regardless of thenocode
flag being set.By adding a simple check we can ensure that the files are only generated if
nocode
is false. Something like..notthetup@5551564
The text was updated successfully, but these errors were encountered: