{"action":"created","issue":{"url":"https://api.github.com/repos/ternjs/tern/issues/684","labels_url":"https://api.github.com/repos/ternjs/tern/issues/684/labels{/name}","comments_url":"https://api.github.com/repos/ternjs/tern/issues/684/comments","events_url":"https://api.github.com/repos/ternjs/tern/issues/684/events","html_url":"https://github.com/ternjs/tern/issues/684","id":116914398,"number":684,"title":"Ditch JSDocs; adopt it's awesome successor, documentationjs","user":{"login":"rozzzly","id":2515134,"avatar_url":"https://avatars.githubusercontent.com/u/2515134?v=3","gravatar_id":"","url":"https://api.github.com/users/rozzzly","html_url":"https://github.com/rozzzly","followers_url":"https://api.github.com/users/rozzzly/followers","following_url":"https://api.github.com/users/rozzzly/following{/other_user}","gists_url":"https://api.github.com/users/rozzzly/gists{/gist_id}","starred_url":"https://api.github.com/users/rozzzly/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rozzzly/subscriptions","organizations_url":"https://api.github.com/users/rozzzly/orgs","repos_url":"https://api.github.com/users/rozzzly/repos","events_url":"https://api.github.com/users/rozzzly/events{/privacy}","received_events_url":"https://api.github.com/users/rozzzly/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-11-14T09:41:43Z","updated_at":"2015-11-14T09:44:52Z","closed_at":null,"body":"Just started using `ternjs`, I LOVE IT. For years I tried to avoid writing `js` because--mainly due to its lack of statically-typed-semantics--the _autocomplete/intellisense/what-have-you_ was a joke. Also because, well, `js` _sucked_ up until a few years ago. I've always relied heavily on this feature and was very excited to discover this project last night. I'm happily using it in `atom` right now. \r\n\r\nHowever, I feel there are still somethings that could be improved here; namely, the documentation support. With my current project, I'm only getting signatures and the small subset of JSDoc syntax that `ternjs` parses currently. I think this is a vital feature! It saves me a bunch of time, I want to improve it. I'd love to see `ternjs` get to the level of say `intellisense` or what `eclipse` has. Providing robust, seamless documentation support would be integral to such an endeavor.\r\n\r\n **Let's face it, JSDocs are pitiful.** The spec leaves is rather skimpy and poorly documented. Use of the de facto standard is not nearly as prevalent as other its counterparts in say, `javadocs`. Tonight I found [**`[documentationjs/documentation]`**](https://github.com/documentationjs/documentation) while trying to figure out how to get `tern` to pickup documentation from/document a nested map/obj. This is awesome.\r\n\r\n> A documentation generation system that's beautiful by default, flexible across formats and styles, and powerful enough to support JSDoc's advanced syntax.\r\n> \r\n> ES5 and ES6 support of JavaScript, with support for other transpilers a possibility\r\n> \r\n> Using babel, we have support for a wide range of ES6 & ES7 features, as well as Flow type annotations.\r\n\r\nIt also can\r\n * automatically link imported dependencies to github sources _we could then grab that very easily_\r\n * export your documentation to json, html, markdown \r\n\r\nIt extends JSDocs into something more modern and has a ton of extra features! I would love to see the JSDoc plugin get revamped to use this package instead. It can still parse tradition JSDocs, so there wont be any messy breaking changes forcing a completely new standard. I think the adoption would be quite easy, and would inevitably lead to both projects continuing to grow.\r\n\r\n[**`[documentationjs/documentation]`**](https://github.com/documentationjs/documentation)  has a lot of overlap with `ternjs` and `acorn`. **Letting the user explicitly define the relationships between bits of code could be used to drastically improve the suggestions!** I could see resolutions becoming much more efficient/accurate _(given the right implementation.)_ I've thought so many potential benefits from this, I just had to make this post. \r\n\r\nI would be happy to contribute towards such an undertaking. I can see there are many #680 other #677 developers #673 who #655 would  #644 probably appreciate this integration as much as I. \r\n\r\nInterested to hear what you all think. :beers: cheers\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/ternjs/tern/issues/comments/156677677","html_url":"https://github.com/ternjs/tern/issues/684#issuecomment-156677677","issue_url":"https://api.github.com/repos/ternjs/tern/issues/684","id":156677677,"user":{"login":"rozzzly","id":2515134,"avatar_url":"https://avatars.githubusercontent.com/u/2515134?v=3","gravatar_id":"","url":"https://api.github.com/users/rozzzly","html_url":"https://github.com/rozzzly","followers_url":"https://api.github.com/users/rozzzly/followers","following_url":"https://api.github.com/users/rozzzly/following{/other_user}","gists_url":"https://api.github.com/users/rozzzly/gists{/gist_id}","starred_url":"https://api.github.com/users/rozzzly/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rozzzly/subscriptions","organizations_url":"https://api.github.com/users/rozzzly/orgs","repos_url":"https://api.github.com/users/rozzzly/repos","events_url":"https://api.github.com/users/rozzzly/events{/privacy}","received_events_url":"https://api.github.com/users/rozzzly/received_events","type":"User","site_admin":false},"created_at":"2015-11-14T09:44:52Z","updated_at":"2015-11-14T09:44:52Z","body":"The one majors implication I see--haven't read too much of the ternjs source yet--is that `ternjs` uses `acorn` while `documentationjs` uses `babel` for it's AST analysis. The two could certainly be fused, and this package has a reaaaaaly strong api too so I'm optimistic. something to chew on"}}