This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Javascript editor fail to apply JsDoc scope tag to a extend pattern's literal object | ||
---|---|---|---|
Product: | javascript | Reporter: | aserron |
Component: | Editor | Assignee: | Martin Fousek <marfous> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.0.1 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
aserron
2011-12-30 17:59:12 UTC
It's also notable that the return type is also lost, by think we could do another report to that issue. I find the solution, "getArr" method should be documented like this. /** * Description text. * @method getArr * @return {Array} An Arr */ Conclusion: 1) @type tag is parsed like field value type, jsDoc handle that by understanding the nature of the "typed" block. Netbeans should either advice this fact or match jsDoc. 2) @method getArr, is needed (i plan to make a wiki on javascript doc, to help users) 3) Both description and return description are ensured, some tests fixes autocomplete when adding them. Switching to enhancement since the scope wasn't supported yet. Actually currently we are parsing that tag, but there is more to do in the model and we haven't time for such improvements this release, sorry. Targeting to next release. I think the parser should be "scope aware" at least try to be. Then the tag could "aid" the parser to define diffuse situations to separate instance time members from the static ones. Also the scope awareness could aid to return a proper type easily. Of course, this are just thoughts i don't know the internals of the engine. (In reply to comment #3) > I think the parser should be "scope aware" at least try to be. > > Then the tag could "aid" the parser to define diffuse situations to separate > instance time members from the static ones. > > Also the scope awareness could aid to return a proper type easily. I agree with all of that. > Of course, this are just thoughts i don't know the internals of the engine. There are two parsers, one for the JS sources, second for the JS documentation. All results must be merged then. And currently we are hardly working on supporting at least the same features as were in the previous release but with the completely new (more buggy and extensible) JS editor. So there's not much place for new enhancement right now, sorry. |