Skip to content

feat(amazonq): hook up showMessage/logMessage/showDocument correctly #5720

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

Merged
merged 1 commit into from
May 15, 2025

Conversation

rli
Copy link
Contributor

@rli rli commented May 14, 2025

logMessage incorrectly piped everything through showMessage, and showDocument did not respect the external flag

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.

logMessage incorrectly piped everything through showMessage, and showDocument did not respect the `external` flag
@rli rli requested a review from a team as a code owner May 14, 2025 19:40
return CompletableFuture.completedFuture(ShowDocumentResult(false))
}

if (params.external == true) {
BrowserUtil.open(params.uri)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this need to be on edt?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no but i dont want to rewrite this and it's not a slow operation

Copy link

Qodana Community for JVM

It 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
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

@rli rli merged commit 2129775 into feature/q-lsp-chat May 15, 2025
14 of 16 checks passed
@rli rli deleted the rli/fix-base-messages branch May 15, 2025 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants