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

IntelliSense beyond bad autocomplete #212021

Closed
4e576rt8uh9ij9okp opened this issue May 4, 2024 · 3 comments
Closed

IntelliSense beyond bad autocomplete #212021

4e576rt8uh9ij9okp opened this issue May 4, 2024 · 3 comments
Assignees
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@4e576rt8uh9ij9okp
Copy link

4e576rt8uh9ij9okp commented May 4, 2024

  • VS Code Version: 1.88.1
  • OS Version: Arch Linux 6.8.7-arch1-1

The IntelliSense autocomplete or suggestion is beyond bad, I don't understand how it chooses what to recommend.
I'm using puppeteer for NodeJS and there is a method named .use() same as in the express module.

I do what everyone else does.

const puppeteer = require('puppeteer')

puppeteer.use

But instead it seeing the use() method it autocompletes to this:
.unregisterCustomQueryHandler
and before pressing enter or closing the brackets, because pressing ( actually is equal to pressing [ENTER], you need to press ESC to NOT apply the autocomplete, so when the autocomplete/intellisense popup shows, this here is striked/crossed like this:
.unregisterCustomQueryHandler
But it still recommends this as a suggestion.

@VSCodeTriageBot
Copy link
Collaborator

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.0. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

@mjbvz
Copy link
Contributor

mjbvz commented May 6, 2024

If use is a valid function, their typings don't show it:

Image

Please file an issue against puppeteer for that.

The rest is just commit characters kicking in. You can disable this using editor.acceptSuggestionOnCommitCharacter

@mjbvz mjbvz closed this as completed May 6, 2024
@mjbvz mjbvz added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label May 6, 2024
@4e576rt8uh9ij9okp
Copy link
Author

If use is a valid function, their typings don't show it:

Image

Please file an issue against puppeteer for that.

The rest is just commit characters kicking in. You can disable this using editor.acceptSuggestionOnCommitCharacter

I have no clue how it works, between a module and vscode IntelliSense. If you say so then I will let them know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

4 participants