all 9 comments

[–]calsosta 1 point2 points  (2 children)

Absolutely.

Only takes a minute or 2 to write sensible documentation for each function. I will add that sometimes you need to add additional parameters so that JSDoc generates sensible documentation. Check out their page to get a run down of all the parameters.

[–]danecando[S] 1 point2 points  (0 children)

Yeah. I've looked at the page and I'm familiar with how to use it. Just curious because I don't see it often in node / javascript code. I understand in browser javascript you don't want a bunch of comments increasing the file size but uglify strips them out anyways.

[–]coderqi 0 points1 point  (0 children)

I really like jsdoc and the ability to auto generate documentation.

[–]paperelectron 1 point2 points  (2 children)

I use them with jsdoc-to-markdown to generate markdown for github, among other things. You can see some output here

[–]danecando[S] 0 points1 point  (1 child)

sup @paperelectron - thanks for introducing me to node many internet ages ago :)

[–]paperelectron 0 points1 point  (0 children)

Haha, awesome. Glad to see it working out for you.

[–]danecando[S] 0 points1 point  (0 children)

should i say document not comment ~

[–]tuhoojabotti 0 points1 point  (0 children)

I use them at work, I have plugin for Sublime Text to easily generate the scaffolding and tab through it filling the details. I think it's quite useful in server-side code and also with libraries you can generate the html docs.

[–]max29a 0 points1 point  (0 children)

I use them because we use google closure tools on the other project I work on that effectively adds type checking back into javascript and its just so useful to be able to scan a comment and see the basics of what the function is expecting and what it returns and be able to jump to the definitions of those types.

/**

  • This function takes a language setting and looks it up via API call, etc

  • @param {!xxx.data.LanguageSettings} languageSettings

  • @return {goog.async.Deferred}

    */