Repository navigation
Simplify manual connections with optional automatic switching - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Manual Connect now offers a checkbox to disconnect the current peer before connecting to the entered number. The preference defaults off and persists per browser/local node. Fresh radio evidence selects a sole peer under the existing control lock; several peers require an explicit choice, and an already-linked target is not disconnected. Favorites and Recent Nodes keep their usual behavior. The old standalone Switch nodes section is removed.
Disconnect and connect reuse the existing verified sequence, stopping on failure. Unknown/stale links never trigger automatic disconnection. The guide describes behavior and failure outcomes. Validation: 27 node-control tests, browser preference/multiple-peer/cancel checks, authenticated and local control routing, saved-node tests, and five-viewport rendering. Applied to the customized live dashboard with backup, served-file verification, and unchanged Asterisk identity; only the dashboard web service restarted. No live radio commands were sent for testing.