You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Typescript language service supports Typescript types in jsdoc. That means that anybody editing Javascript code with the Typescript language service, such as users of VS Code, Webstorm, Visual Studio, Sublime, Vim or Emacs, will expect eslint rules to understand Typescript types. Since eslint-plugin-jsdoc is the now-recommended way to lint jsdoc, and it relies on jsdoctypeparser, jsdoctypeparser should parse Typescript types.
Here's a list of the types that I've found so far that need support:
The Typescript language service supports Typescript types in jsdoc. That means that anybody editing Javascript code with the Typescript language service, such as users of VS Code, Webstorm, Visual Studio, Sublime, Vim or Emacs, will expect eslint rules to understand Typescript types. Since eslint-plugin-jsdoc is the now-recommended way to lint jsdoc, and it relies on jsdoctypeparser, jsdoctypeparser should parse Typescript types.
Here's a list of the types that I've found so far that need support:
[string, string][a: string, b: string][...A, ...B](x: string) => number{ x: string, (some: string, func: string) => void }{ staticX: string, new (some: string, ctor: string): C }import("./package").Type{ [K in keyof T]: Boxed<T[K]> }A extends B ? C : Dtypeof someVariable{ readonly a: string }<T>(a: T) => TA & Bparam is Typeasserts param is TypeI've got type queries working and import types mostly working, so I'll probably create a PR for those before continuing with the rest.