Native LS: JSDoc @this / @param types are any for hover & completions (checker OK) #65167

Activity

1. timurzvural commented on Nov 3, 2026

   

   Timur Vural (timurzvural)

   on Nov 3, 2026

   Author

   More actions

   Broader than @this

   Same native LS hole for JSDoc @param types on JS function parameters: checker diagnostics see the type, but hover/completions treat the parameter as any.

   // @allowJs: true
   // @checkJs: true
   /**
    * @param {{ id: string }} p
    */
   function f(p) {
     p./*completions: classic offers id; native nil*/
     p.missing; // both: TS2339 — checker is fine
   }

   Native hover on p: (parameter) p: any
   Classic hover on p: (parameter) p: { id: string; }

   Controls that work on native:

   • TS this / parameter annotations
   • JSDoc @type on const/var with an initializer (or assigned before use)
   • Plain inferred object literals in .js

   So the gap is specifically LS display/completions for types attached via JSDoc to parameters / this, not all JSDoc typing.
2. Timur Vural (timurzvural)

   changed the title [-]Native LS: no property completions on `this.` when type comes from JSDoc `@this`[/-] [+]Native LS: JSDoc `@this` / `@param` types are `any` for hover & completions (checker OK)[/+] on Nov 3, 2026
3. timurzvural commented on Nov 3, 2026

   

   Timur Vural (timurzvural)

   on Nov 3, 2026

   Author

   More actions

   Also signature help

   Call-site signature help for the same JSDoc-@param-typed function shows any parameters on native:

   /**
    * @param {string} a
    * @param {number} b
    */
   function f(a, b) {}
   f(/* signature help here */

   • Classic: f(a: string, b: number): void
   • Native: f(a: any, b: any): void
4. Ryan Cavanaugh (RyanCavanaugh)

   added

   BugA bug in TypeScriptA bug in TypeScript

   on Nov 3, 2026
5. Ryan Cavanaugh (RyanCavanaugh)

   added this to the Backlog milestone on Nov 3, 2026
6. 1-DARK commented on Nov 4, 2026

   

   Harsh Vardhan Chauhan (1-DARK)

   on Nov 4, 2026

   Contributor

   More actions

   Thanks for the detailed report. As far as I can tell this isn't an LS bug; the repro just isn't running in a JS file.

   The fourslash snippets have @allowJs/@checkJs but no // @filename: /something.js, so the content isn't treated as JS. In TS files, JSDoc @this/@param types aren't used for typing, so this/p being any (and no member completions) is expected there.

   With an explicit JS filename, everything in this issue and the follow-up comments already works on native main:

   // @allowJs: true
   // @checkJs: true
   // @filename: /a.js
   /**
    * @this {{ id: string, click: () => void }}
    * @param {{ name: string }} p
    */
   function h(p) {
     this./*→ click, id*/;
     p./*→ name*/;
   }
   /**
    * @param {string} a
    * @param {number} b
    */
   function f(a, b) {}
   f(/*→ f(a: string, b: number): void*/);

   Hover on p shows (parameter) p: { name: string; }. I've added this as a fourslash regression test in #65307. Suggest closing as not a bug; please reopen if you can reproduce it with a real .js file in an editor.