| ▲ | c-hendricks a day ago | |||||||
Apologies, my first draft of that comment got deleted on a refresh (mobile) and my posted one left out how I'm probably being too pedantic: the official JSDoc is not TypeScript. Your post is actually one of the more accurate ones compared to others that say "you don't need typescript" with the big caveat that you actually need a whole lot of the typescript ecosystem to make JSDoc work. I just wish there was an official handover, or a more clear delineation between JSDoc and Typescript JSDoc Extensions. | ||||||||
| ▲ | culi a day ago | parent [-] | |||||||
I think you have a valuable point. I kinda purposely avoided explicitly defining what JSDoc is. Instead I'm relying on "the JSDoc we're all familiar with". I said in the post that if your IDE is giving you intellisense from JSDoc comments then you are almost certainly already using TypeScript. That's about as close as I got to defining the JSDoc I'm talking about But given that JSDoc doesn't have any sort of formal spec, I think the distinction you're making is more of a historical than a technical one. | ||||||||
| ||||||||