Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324869 - JavaScript Generics: @returns {Array<Type>}
Summary: JavaScript Generics: @returns {Array<Type>}
Status: RESOLVED WONTFIX
Alias: None
Product: JSDT
Classification: WebTools
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement with 3 votes (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Nitin Dahyabhai CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-09 12:28 EDT by domcap CLA
Modified: 2011-07-01 04:23 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description domcap CLA 2010-09-09 12:28:30 EDT
Build Identifier: 20100617-1415

The content assist in Eclipse works really well until you hit a method that returns arrays, at which point there is no way to inform Eclipse which type of object the array consists of. I'd like to propose the following (Java Generics style) notation for allowing this:

  @returns {Array<Type>} comment

This would work immediately in jsdoc-toolkit and jsdoc.pl since it will just be interpreted as a string, but could also be supported more thourougly later, allowing hyperlinking of the type within the angle brackets.


Reproducible: Always
Comment 1 Philippe Marschall CLA 2011-04-16 18:12:18 EDT
jsdoc-toolkit seems to use the following notation 

@returns {Type[]}

http://code.google.com/p/jsdoc-toolkit/wiki/TagParam#Parameter_Type_Information
Comment 2 Nitin Dahyabhai CLA 2011-06-30 17:28:03 EDT
As linked in comment 1, there's a set format for the documentation we support.  We're not going to invent/extend one and make people use it.  Recommend advocating for something like this in JSDoc 3 (or 4?) and then we'll look into using it.
Comment 3 Philippe Marschall CLA 2011-07-01 03:00:09 EDT
I'm a bit confused, it's in JSDoc 2
http://code.google.com/p/jsdoc-toolkit/wiki/TagParam#Parameter_Type_Information
so I'm not sure why there is a need to advocate this in JSDoc 3 (or 4).
Comment 4 domcap CLA 2011-07-01 04:23:03 EDT
@Nittin
You've closed this bug as won't fix but you also don't support the jsdoc array notation that other people have mentioned on this issue. Should I raise another issue for that instead?

@Philippe
I assume the reason Nittin is saying that I should ask for it in jsdoc v3 (or v4) is that the notation I was suggesting was more powerful as it allows typed maps too. As it happens, I didn't know about the jsdoc array notation since I'm still using jsdoc-pl (rather than jsdoc-toolkit), which doesn't have support for either notation.