Skip to content
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

Is it possible to add tooltip hints for common *.conf.js? #24657

Closed
Deilan opened this issue Apr 13, 2017 · 4 comments
Closed

Is it possible to add tooltip hints for common *.conf.js? #24657

Deilan opened this issue Apr 13, 2017 · 4 comments
Assignees
Labels
feature-request Request for new features or functionality javascript JavaScript support issues *out-of-scope Posted issue is not in scope of VS Code typescript Typescript support issues

Comments

@Deilan
Copy link

Deilan commented Apr 13, 2017

Is it possible to add tooltip hints for common *.conf.js in a similar fashion it is done for package.json tsconfig.json, etc.? For example, karma.conf.js, protractor.confg.js, etc. I understand that it's not a regular json file, but such a capability would greatly help.

@Deilan Deilan changed the title Is it possible to add tooltip hints for common *.conf.js Is it possible to add tooltip hints for common *.conf.js? Apr 13, 2017
@mjbvz mjbvz added javascript JavaScript support issues typescript Typescript support issues feature-request Request for new features or functionality labels Apr 14, 2017
@mjbvz
Copy link
Collaborator

mjbvz commented Apr 14, 2017

Related to #24270 which tracks this for webpack config files. In some cases, you may be able to use jsdocs to get better intellisense:

import { Configuration } from 'webpack'

/**
 * @type {Configuration}
 */
const config = {
    
};

module.exports = config

However this TypeScript bug prevents the typings from being very useful

@JasCodes

This comment has been minimized.

@mjbvz
Copy link
Collaborator

mjbvz commented Oct 3, 2020

Closing this due to lack of further community interest over the past few years.

You should now be able to use JSDoc type annotations in most cases (the linked TS issue above has been fixed for a long time). Adding a jsdoc type will get you better intellisense and optional type checking as well

@mjbvz mjbvz closed this as completed Oct 3, 2020
@mjbvz mjbvz added the *out-of-scope Posted issue is not in scope of VS Code label Oct 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality javascript JavaScript support issues *out-of-scope Posted issue is not in scope of VS Code typescript Typescript support issues
Projects
None yet
Development

No branches or pull requests

4 participants
@JasCodes @Deilan @mjbvz and others