Fix/profile rename change detection

[NoahJenkins]

This fix addresses a UI bug where the save button remained disabled after renaming an API configuration profile in the Settings view. The issue arose because profile rename operations didn’t trigger the change detection mechanism, preventing users from saving their changes.

Changes Made:

• SettingsView.tsx: Added setChangeDetected(true) in the onRenameConfig callback to properly trigger change detection when profiles are renamed.
• SettingsView.spec.tsx: Added a comprehensive test suite covering profile rename scenarios.

Test Coverage Added:

• Save button enablement when a profile is renamed.
• VSCode message sending on rename operations.
• Save functionality after a profile is renamed.
• Save button state after a successful save.
• Unsaved changes dialog when navigating away.
• Dialog interaction (discard vs cancel) behavior.

Problem Solved:

Before: Users could rename profiles, but the save button remained disabled, preventing them from persisting changes.
After: Renaming a profile now properly enables the save button and integrates with the existing change detection system, including unsaved changes warnings.

Technical Details:

The fix ensures that profile rename operations are treated as change events, triggering the change detection mechanism and allowing users to save their changes.
Modifications that require saving are now tracked alongside other UI settings changes. The change detection mechanism now properly tracks profile renames.

---

Important

Fixes issue in SettingsView.tsx where renaming a profile did not enable the save button, and adds comprehensive tests for profile rename scenarios.

• Behavior:
  • Fixes issue in SettingsView.tsx where renaming a profile did not enable the save button.
  • Adds setChangeDetected(true) in onRenameConfig callback to trigger change detection.
• Tests:
  • Adds tests in SettingsView.spec.tsx to cover profile rename scenarios.
  • Tests include save button enablement, VSCode message sending, save functionality, unsaved changes dialog, and dialog interaction behavior.
• Problem Solved:
  • Previously, users could not save changes after renaming a profile due to disabled save button.
  • Now, renaming a profile enables the save button and integrates with change detection.

^{This description was created by for 47b40dd. You can customize this summary. It will automatically update as commits are pushed.}

[Copilot]

Pull Request Overview

This PR fixes a UI bug where the save button remained disabled after renaming an API configuration profile in the Settings view. The issue was that profile rename operations didn't trigger the change detection mechanism.

• Added setChangeDetected(true) in the onRenameConfig callback to properly trigger change detection
• Added comprehensive test coverage for profile rename scenarios
• Ensured profile renames integrate with the existing change detection system including unsaved changes warnings

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
SettingsView.tsx	Added change detection trigger when profiles are renamed
SettingsView.spec.tsx	Added comprehensive test suite covering profile rename change detection scenarios

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[roomote]

Thank you for your contribution! I've reviewed the changes and found that while the core fix is correct, there are some issues that need attention before merging.

[daniel-lxs]

I'm unable to reproduce the issue, I can save the API profile without any issue and the change is reflected without any problems:



The little checkmark button is the save button for the rename.

This might be a bit confusing but I would recommend opening a new issue for that, let me know if you have any questions!