mirror of
https://github.com/lukaszraczylo/kportal.git
synced 2026-10-12 04:35:10 +00:00
Previously, editing a forward and keeping its local port unchanged failed the wizard's port-availability check: the in-config scan found the forward's own entry and reported '✗ Port N already assigned to <self.ID>'. Users had to pick a different port, edit, then change back. checkPortCmd now accepts an excludeID. The wizard passes wizard.originalID when isEditing so the forward being edited is ignored during the in-config conflict scan. The OS-level port check is unchanged (still catches actual port collisions). New regression test: TestCheckPortCmd_ExcludeID_AllowsKeepingOwnPort.