Skip to content

fix(connections): allow duplicate connection names - #90

Merged
oesukam merged 1 commit into
mainfrom
fix/allow-duplicate-connection-names
Aug 4, 2026
Merged

fix(connections): allow duplicate connection names#90
oesukam merged 1 commit into
mainfrom
fix/allow-duplicate-connection-names

Conversation

@oesukam

@oesukam oesukam commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

Reported: 'A connection with this name already exists.' when the name isn't actually a duplicate — and more broadly, duplicate names should just be allowed.

The validator rejected any name matching an existing connection (case-insensitive). That blocks legitimate cases — several connections to the same host, or simply not caring about unique labels. Drop the uniqueness check; only a non-empty name is required.

Test updated (259 unit tests pass).

The form rejected a name matching any existing connection ('A connection
with this name already exists.'), which blocked saving even when the
duplicate was intentional (several connections to the same host, or just
not caring about unique labels). Drop the uniqueness check — only require
a non-empty name. Tests updated.
@oesukam
oesukam merged commit 1f455de into main Aug 4, 2026
6 checks passed
@oesukam
oesukam deleted the fix/allow-duplicate-connection-names branch August 4, 2026 16:20
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