-
Notifications
You must be signed in to change notification settings - Fork 12.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JavaScript Property Suggestions Do not Pick Up Type From JSDoc Comment #13333
Comments
Looks like a TS issue, unrelated to webpack and imports. Tested with 2.1.5 and 2.2.0-dev.20170106 Here's a simpler repo: interface IFoo {
bar: number
}
/** @type {IFoo} */
const foo = {
} When typing inside of interface IFoo {
bar: number
}
const foo: IFoo = {
} then Here's the TSServer communications in the bad case:
|
Ran into similar problem, and just wanted to point out that I have imported types as follows. And this (workaround?) works pretty well in vscode v1.35.0-insider. const HtmlWebpackPlugin = require('html-webpack-plugin');
const baseUrl = "/";
/** @type {() => import("webpack").Configuration} */
module.exports = () => ({
plugins: [
new HtmlWebpackPlugin({
template: "index.ejs",
metadata: { baseUrl }
})
]
}) |
Yes the |
From @mohsen1 on January 5, 2017 18:28
Steps to Reproduce:
loaders
.Copied from original issue: microsoft/vscode#18184
The text was updated successfully, but these errors were encountered: