Skip to content

fix(ui): allow deleting saved module API-keys [closes #15] - #120

Draft
robotyaga-gigachain[bot] wants to merge 1 commit into
mainfrom
open-swe/delete-module-api-keys
Draft

fix(ui): allow deleting saved module API-keys [closes #15]#120
robotyaga-gigachain[bot] wants to merge 1 commit into
mainfrom
open-swe/delete-module-api-keys

Conversation

@robotyaga-gigachain

@robotyaga-gigachain robotyaga-gigachain Bot commented Jul 8, 2026

Copy link
Copy Markdown

Description

Masked pass-type module API-keys (e.g. the VK token) in Settings → Основные → «API-ключи модулей» could not be removed once saved: focusing the field cleared the mask, but an empty value was treated as "no change" on save, so the key persisted (the only workaround was typing random characters). This adds a per-field clear (×) button that explicitly marks the secret for deletion and sends an empty value, which the backend interprets as clearing the key. Verified end-to-end (set key → clear via button → save → backend reports filled: false).

Release Note

Saved module API-keys can now be removed directly via a clear (×) button in Settings.

Test Plan

  • In Settings → Основные, save a module API-key (e.g. VK), reload, click the × button on that key, and Save — confirm the key is removed and stays removed after reload.
  • Confirm the × button only appears for keys that have a value, and typing a new value hides it / overrides deletion.

Masked "pass"-type module secrets (e.g. VK_TOKEN) could not be removed:
clicking the field cleared it to empty, but an empty value was treated as
"no change" on save, so the key persisted. Add a per-field clear (×) button
that explicitly marks the secret for deletion and sends an empty value so the
backend clears it.

Closes #15

Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>

@robotyaga-gigachain robotyaga-gigachain Bot left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

✅ Open SWE Review: No issues found

Open SWE reviewed this PR and found no potential bugs to report.

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.

1 participant