-
Notifications
You must be signed in to change notification settings - Fork 251
fix(amazonq): avoid using modeled types in chat message proxy #5710
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
There is a high possibiltiy of drift in our modeling as the UI <-> Server evolves. To avoid a treadmill in making sure these are always up to date, avoid materializing these messages into concrete types
Qodana Community for JVM5 new problems were found
💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at qodana-support@jetbrains.com
|
} | ||
} | ||
|
||
val sendChatPrompt = JsonRpcRequest( |
Check warning
Code scanning / QDJVMC
Unused symbol Warning
String::class.java | ||
) | ||
|
||
val sendQuickAction = JsonRpcRequest( |
Check warning
Code scanning / QDJVMC
Unused symbol Warning
Any::class.java | ||
) | ||
|
||
val getSerializedActions = JsonRpcRequest( |
Check warning
Code scanning / QDJVMC
Unused symbol Warning
fun <T> executeIfRunning(project: Project, runnable: AmazonQLspService.(AmazonQLanguageServer) -> T): T? = | ||
project.serviceIfCreated<AmazonQLspService>()?.executeSync(runnable) | ||
|
||
suspend fun <T> asyncExecuteIfRunning(project: Project, runnable: suspend AmazonQLspService.(AmazonQLanguageServer) -> T): T? = |
Check warning
Code scanning / QDJVMC
Unused symbol Warning
val error: OpenTabResultErrorError, | ||
) | ||
|
||
data class OpenTabResultErrorError( |
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.
nit:
data class OpenTabResultErrorError( | |
data class OpenTabResultErrorData( |
There is a high possibiltiy of drift in our modeling as the UI <-> Server evolves.
To avoid a treadmill in making sure these are always up to date, avoid materializing these messages into concrete types
License
I confirm that my contribution is made under the terms of the Apache 2.0 license.