Skip to content

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

Merged
merged 59 commits into from
Apr 21, 2025

Conversation

evanliu048
Copy link
Contributor

@evanliu048 evanliu048 commented Apr 16, 2025

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

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

  • My code follows the code style of this project
  • I have added tests to cover my changes
  • A short description of the change has been added to the CHANGELOG if the change is customer-facing in the IDE.
  • I have added metrics for my changes (if required)

License

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

@evanliu048 evanliu048 marked this pull request as ready for review April 18, 2025 19:51
@Will-ShaoHua
Copy link
Contributor

@evanliu048 evanliu048 requested a review from Will-ShaoHua April 18, 2025 21:55
@evanliu048 evanliu048 requested a review from rli April 21, 2025 17:04
@@ -12,4 +13,7 @@ data class CodeWhispererCustomization(

@JvmField
var description: String? = null,

@JvmField
Copy link
Contributor

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?

Copy link
Contributor Author

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.

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.

4 participants