-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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 suggestions are currently too intrusive #26340
Comments
One option we have in the interim is to add this setting to your settings:
That will place snippet suggestions higher in the sort order. |
Whoa - that's 99% of what I need. Thanks a ton @seanmcbreen |
@mhegazy We've seen a few requests similar to this about reducing the number of completions in JavaScript contexts. I prototyped a simple filter, but there are a few complications:
We should be able to workaround the first issue on the VSCode side but the second would require a TS change. There may be other problems that I haven't considered here. Any thoughts on this? |
Filtering should be done on the TS side of things. We should be able to filter compleations based on what the location allow. |
@mjbvz can you please port this to the TS repo? |
Opened microsoft/TypeScript#15750 to track reducing the number of type suggestions in js files Closing as upstream |
Fair enough - are you sure this couldn't be solved more easily in VS Code though? Ie, just expose all the sources of these suggestions and let users blacklist as many or as few as desired? |
Steps to Reproduce:
Related to this Stack Overflow question: http://stackoverflow.com/questions/43850267/configure-visual-studio-code-suggestions/
It would be ideal to be able to see all sources for these suggestions, and be able to turn them off. Or any other workarounds would be much appreciated too! I selected the highlighted option in the image and tried to "go to definition" but none was found, so it appears to be really tricky tracking down the .d.ts file where these are coming from.
The text was updated successfully, but these errors were encountered: