-
Notifications
You must be signed in to change notification settings - Fork 75
feat: add ide category to auto-trigger threshold computation #1104
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
Conversation
JB and VSC need different IDE cofficients for auto trigger threshold
server/aws-lsp-codewhisperer/src/language-server/inline-completion/codeWhispererServer.ts
Outdated
Show resolved
Hide resolved
other IDE's value should be 0
'AmazonQ-For-VSCode': 'VSCODE', | ||
'Amazon-Q-For-JetBrains': 'JETBRAINS', | ||
'Amazon Q For JetBrains': 'JETBRAINS', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this inconsistency caused by? Cannot we pass extension name for JetBrains in clientInfo
following the same format as for other IDEs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The extension name for JetBrains is "Amazon Q For JetBrains", with spaces, not sure why the version with hyphens are added there, this is tested with Jb talking to flare,
For Eclipse and VS, they should be already talking to flare so assuming the names are correct, for VSC I'm not sure, it will be determined when we decide to move VSC inline to flare.
JB and VSC need different IDE cofficients for auto trigger threshold
Problem
JB and VSC need different IDE cofficients for auto trigger threshold
Solution
Pass IDE category as the parameter and get different coefficient based on this info
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.