(sorry for delay, I just see this post never arrived because of wrong sender)
Thanks for such a detailed reply.
Le 11/06/12 à 23:21, Michael Mathews <
mic...@gmail.com> a écrit :
MM> A "module," as JSDoc understands it, is defined in the CommonJS Modules standard. This says
MM> that a module identifier is a String of "terms" delimited by forward slashes, and that a
MM> global "require" function accepts that module identifier. These identifiers are often
MM> related to the filepath of the file containing the module source.
MM>
MM> The code you've written does not reflect this understanding of what a module is. In JSDoc
MM> terms, it would be more accurate to call "ns.myFirstModule" a (nested) namespace. In short,
MM> the default template for JSDoc will not display modules as members of any other object,
MM> they must be global and must be identified by a string.
It's right, I shouldn't use the "module" term because this sample code isn't reflecting a
module as CommonJS Modules standard defined it (it's the same with our real code).
So, is there any solution to see this code (it's perhaps not the best way coding js but it's the
code we have) documented with jsdoc ?
I can change the doc tags but I don't want to change deeply the code (of course I can change
"M.funcOne = function()" by "function funcOne(); M.funcOne = funcOne;", but it's not enough te
see this code documented).
Thanks a lot
--
Daniel
L'équipe de France de football est très appréciée : toutes les autres équipes
veulent la rencontrer.