-
Notifications
You must be signed in to change notification settings - Fork 269
fix(amazonq): delete AwsServerCapabilitiesProvider #5833
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
Qodana Community for JVM1 new problem were found
💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at [email protected]
|
.../jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/webview/Browser.kt
Fixed
Show fixed
Hide fixed
.../jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/webview/Browser.kt
Fixed
Show fixed
Hide fixed
…ovider Conflicts: plugins/amazonq/shared/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/lsp/AmazonQLspService.kt
…ovider Conflicts: plugins/amazonq/chat/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/webview/BrowserConnector.kt plugins/amazonq/shared/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/lsp/model/ExtendedClientMetadata.kt plugins/amazonq/shared/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/lsp/model/aws/AwsServerCapabilities.kt
Qodana Community for JVMIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at [email protected]
|
It is not actually needed; we can read the values from AmazonQLspService
…alter behavior of explain and fix buttons (#5970) * feat(amazonq): add support for CodeReview and DisplayFindings tools, alter behavior of explain and fix buttons * fix(amazonq): remove commented lines * feat(amazonq): add support for CodeReview and DisplayFindings tools, alter behavior of explain and fix buttons * fix(amazonq): remove commented lines * fix(amazonq): general code quality fixes for CodeReview and DisplayFindings tools * fix(amazonq): Prevents Q UriError : Validate file URI and fallback to Path.toUri() for WSL (#5960) Fix repeated UriError when Amazon Q starts with a WSL-backed workspace. We now validate the constructed file: URI and fallback to JDK’s Path.toUri() if the URI violates Rule (no authority while the path begins with //, maybe RFC 3986). This keeps legacy behavior where it’s safe, and prevents Q from rejecting the workspace folder URI * feat(amazonq): show the opt-in checkbox for server-side context (#5894) We need to support client-side opt-out for internal users who have workspace context server running by default. * fix(amazonq): delete AwsServerCapabilitiesProvider (#5833) It is not actually needed; we can read the values from AmazonQLspService * feat(amazonq): add support for CodeReview and DisplayFindings tools, alter behavior of explain and fix buttons * Revert "feat(amazonq): add support for CodeReview and DisplayFindings tools, alter behavior of explain and fix buttons" This reverts commit f21c028. * fix(amazonq): fix formatting issues * fix(amazonq): fix more formatting issues * fix(amazonq): fix build failures * fix(amazonq): undo unrelated change * fix(amazonq): address codeReview comments * fix(amazonq): fixing detekt errors * feat(amazonq): emit telemetry events for explainIssue and applyFix commands * feat(amazonq): add unit tests for parseFindingsMessage * fix(amazonq): fix detekt errors * fix(amazonq): fix re-direct of /review action * fix(amazonq): improve handling of case where messageId is null * fix(amazonq): Add changelog, code quality improvements * fix(amazonq): address comments * fix(amazonq): remove unused import --------- Co-authored-by: Blake Lazarine <[email protected]> Co-authored-by: Lee Won Jun <[email protected]> Co-authored-by: Jiatong Li <[email protected]> Co-authored-by: Richard Li <[email protected]> Co-authored-by: Laxman Reddy <[email protected]>
It is not actually needed; we can read the values from AmazonQLspService
License
I confirm that my contribution is made under the terms of the Apache 2.0 license.