It seems this is related to getting JSDoc for contextually-typed object literals. This should likely work just as you'd expect.

Pretty sure that this issue is what I'm hitting with this type of code:

const someFunc = () => {
    return {
        /** This JSDoc comment doesn't leave the function */
        one: "1",
        /** Neither does this */
        two: "2"
    }
}

const a = someFunc()

a.one
// ^?

type A = ReturnType<typeof someFunc>
//   ^?

Both

Workbench Repro

I realize now that the // ^? doesn't show JSDoc anyway, so the repro is useless 🍡

@johnnyreilly do you remember what this was about? I would imagine this:

interface Foo {
    /**
     * Hallo this is JSDoc
     */
    yadda(): void
}

let x: Foo = {
    yadda() {

    }
}

which seems to be fixed.

@orta if I hover on that in the playground, that seems to work.

Wow - this an old issue! I do vaguely remember raising it - but not more than that. The way intellisense is powered in Visual Studio has radically changed now I understand. I should say I haven't used VS in about four years though. Apologies

👋 Hi, I'm the Repro bot. I can help narrow down and track compiler bugs across releases! This comment reflects the current state of this repro running against the nightly TypeScript.

Comment by @orta

⚠️ Assertions:

• (property) one: string
• type A = { one: string; two: string; }

@DanielRosenwasser @johnnyreilly I've tried a couple of things in VS Code and all basic cases seem to work just fine nowadays. It's probably best to close this issue as it was most likely fixed along the way.