Open kurideja opened 9 years ago
nope ... in fact, id love to see some guidelines with some code setup isntructions on how to use jdoc in this issue to help folks use it with the guide. interested in helping contribute that and adjusting the guide with a PR for any changes needed?
Will look into it next week ;)
looking forward to this!
Is there anyone working on this? otherwise I would like to enhance the JSDoc section.
@Nazanin1369 , I got extremely busy after opening the ticket. Feel free to work on this.
@kurideja sure.
@johnpapa removed the descriptions in last commit. Do we want to include an example from ngdoc also?
IMO it will be clear with an example :smile:
anyone want to make a PR for this?
Hey @johnpapa , it's been more than a year since I opened this thread 😞
Take a look at my JSDoc gist.
We seem to like it this way at work. Not using @memberOf
or @namespace
didn't seem like an issue so far with multiple and rather big projects.
If we are on the same page, I could start PRs in some time.
I was wondering about types/constructors. Here you suggest {String} as type definition for a string parameter. The original JSDoc seems to use lowercase type names for scalars and uppercase constructor names for Objects or Arrays.
Is there any particular reason you define string with constructor name (String) rather than its type (string)?