JSDoc bugs? @typedef and @name

I found what appeared to be a couple of bugs (to do with jsdoc and proper recognition of @typedef and @name) and logged them on the bug tracker. Thought I'd also raise it on the forum so as to get a bit of feedback as to whether they are bugs or if I'm just doing something wrong.

http://youtrack.jetbrains.com/issue/WEB-11189

http://youtrack.jetbrains.com/issue/WEB-11190

Cheers.

3 comments
Comment actions Permalink

Hello!

some issues related ro @typedef are fixed in WebStorm8. See the updated tickets

0
Comment actions Permalink

Hi Elena

Thanks for your reply.

I just downloaded and tried WebStorm 8 EAP. I retested, found some issues, and posted a new ticket.

http://youtrack.jetbrains.com/issue/WEB-11231

The whole JSDoc concept and attempt to support is fantastic. However, going back to WebStorm version 6, there have been issues related to types defined with ! and ? and it is a little frustrating to see those issues still persist in version 7 let alone version 8. I expected a complete overhaul and fix in version 7, was disappointed upon its release, then thought for sure the next version would completely deal with the issues once and for all. Unfortunately, that has not happened either. That would seem to indicate that resources for the task are in short supply (presumably to work on items with a higher priority - fair enough). I would be happy to put time into that portion of the development (i.e. JSDoc parsing - specification and/or development). Is there a way to contribute?

Cheers.

0
Comment actions Permalink

Don't think this was fixed in WebStorm 10 - see my comment at https://youtrack.jetbrains.com/issue/WEB-11189

0

Please sign in to leave a comment.