We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At the moment we send a new AI request for every keystroke in the editor. This is unnecessary and uses up a lot of resources/tokens.
We should investigate some sort of debounce mechanism, in which requests are not event sent when a new keystroke already came in.
The entry point of the code can be found here
Debouncing for 200ms or more seems sensible. The skipped completions should then likely return an empty items array.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Feature Description:
At the moment we send a new AI request for every keystroke in the editor. This is unnecessary and uses up a lot of resources/tokens.
We should investigate some sort of debounce mechanism, in which requests are not event sent when a new keystroke already came in.
The entry point of the code can be found here
Suggested solution
Debouncing for 200ms or more seems sensible. The skipped completions should then likely return an empty items array.
The text was updated successfully, but these errors were encountered: