-
Notifications
You must be signed in to change notification settings - Fork 251
fix(amazonq): support displaying customizations across all profiles of an Idc connection #5591
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
# Conflicts: # plugins/amazonq/shared/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/profile/QRegionProfileManager.kt
# Conflicts: # plugins/core/sdk-codegen/codegen-resources/codewhispererstreaming/service-2.json
# Conflicts: # plugins/core/sdk-codegen/codegen-resources/codewhispererstreaming/service-2.json
...ws/toolkits/jetbrains/services/codewhisperer/customization/CodeWhispererModelConfigurator.kt
Outdated
Show resolved
Hide resolved
...re/aws/toolkits/jetbrains/services/codewhisperer/customization/CodeWhispererCustomization.kt
Show resolved
Hide resolved
...munity/src/software/aws/toolkits/jetbrains/services/amazonq/profile/QRegionProfileManager.kt
Outdated
Show resolved
Hide resolved
...munity/src/software/aws/toolkits/jetbrains/services/amazonq/profile/QRegionProfileManager.kt
Show resolved
Hide resolved
...mmunity/src/software/aws/toolkits/jetbrains/services/amazonq/profile/QProfileSwitchIntent.kt
Outdated
Show resolved
Hide resolved
.../toolkits/jetbrains/services/codewhisperer/customization/CodeWhispererCustomizationDialog.kt
Show resolved
Hide resolved
.../toolkits/jetbrains/services/codewhisperer/customization/CodeWhispererCustomizationDialog.kt
Show resolved
Hide resolved
...ws/toolkits/jetbrains/services/codewhisperer/customization/CodeWhispererModelConfigurator.kt
Outdated
Show resolved
Hide resolved
...ws/toolkits/jetbrains/services/codewhisperer/customization/CodeWhispererModelConfigurator.kt
Outdated
Show resolved
Hide resolved
...ws/toolkits/jetbrains/services/codewhisperer/customization/CodeWhispererModelConfigurator.kt
Outdated
Show resolved
Hide resolved
@@ -12,4 +13,7 @@ data class CodeWhispererCustomization( | |||
|
|||
@JvmField | |||
var description: String? = null, | |||
|
|||
@JvmField |
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.
do we remember why these need to be fields?
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.
I followed the style of other fields in the file. It might be good to check with @Will-ShaoHua or @manodnyab in case they have more context on why this pattern is used.
Follow-up to #5575.
As mentioned in that PR:
Before: Customizations were bound to a specific IDC instance.
After: Customizations are now bound to a specific Q profile. An IDC instance can have multiple Q profiles.
In other words, each Q profile has access to its own set of customizations.
Types of changes
Description
The product team has requested that we show all available customizations across profiles, rather than only those tied to the currently connected profile.
This means that when a user selects a customization that belongs to a different Q profile, the plugin should implicitly switch to that profile. This behavior helps reduce confusion and user churn, since users might not clearly understand which profile grants access to which customizations.
Summary of Changes
- Display all customizations across profiles.
Screen.Recording.2025-04-20.at.11.56.42.PM.mov
- Change profile should validate if the selected customization is under the new profile or not
Screen.Recording.2025-04-20.at.11.57.08.PM.mov
Checklist
License
I confirm that my contribution is made under the terms of the Apache 2.0 license.