Community
Participate
Working Groups
Build Identifier: The @extends and @base jsdoc annotations allow developers to signal the class inheritance for code bases that perform the inheritance using some library methods, rather than direct javsascript prototype inheritance. These annotations were made use of in Eclipse Galileo, but no longer appear to work in Helios M7. Reproducible: Always Steps to Reproduce: 1. Create a Child class which extends a defined Parent class 2. use the @extends or @base annotations rather than doing direct javascript inheritance 3. proove that content assist starting with '(new Child()).' does not display the methods defined on Parent.
Build Identifier: 20100506-2000
Any news on this?
Can you provide some sample code you expect to work?
Seems to work as long as the @constructor tag is also present.
Created attachment 171743 [details] test case 1
Created attachment 171744 [details] test case 2
Created attachment 171745 [details] test case 3
Okay, so this turns out to only go wrong when package names are being used to namespace your classes. Since all of our code is contained within packages that wasn't immediately obvious to me. Thanks for all your help everyone.
It's been pointed out to me that my last comment may have made it sound like this was not an actual problem. To be clear here, this is a bug, and it's a regression from Galileo. Our company and our clients (API users) are all very keen to start making use of Eclipse's new Javascript code completion features, but will be unable to do so unless this bug is fixed. Thanks again, Dominic.
Created attachment 172631 [details] patch Uses the full type name instead of simple type name in the case where namespaces are being used.
Nitin, Please review. Simple fix to use the full type name pkg2.BaseClass instead of the simple name when creating the type hierarchy. I have marked for 3.2.1. This fix solves the problems indicated by the test cases.
Patch checked in.
Is there any way to test nightly builds of the JSDT component? Every few days I try to upgrade my JSDT component from within Eclipse but it seems to be stuck on '1.2.0.v201005270528-7C78FGDF9JgLWLMBWz-Ose6'. Thanks again, Dominic.
(In reply to comment #13) > Is there any way to test nightly builds of the JSDT component? Every few days I > try to upgrade my JSDT component from within Eclipse but it seems to be stuck > on '1.2.0.v201005270528-7C78FGDF9JgLWLMBWz-Ose6'. > > Thanks again, Dominic. Builds can be found here: http://build.eclipse.org/webtools/committers/