Skip to content

Get-WebSocket should use the -Force #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
StartAutomating opened this issue Jan 9, 2025 · 0 comments
Closed

Get-WebSocket should use the -Force #58

StartAutomating opened this issue Jan 9, 2025 · 0 comments
Assignees
@StartAutomating
Labels
enhancement New feature or request
Milestone
WebSocket-Server

Comments

@StartAutomating
Copy link
Member

As with many PowerShell parameters, this may indicate many things.

To start off with, it will "Force" the creation of a new WebSocket connection, regardless of if one is already open ( #35 )
@StartAutomating StartAutomating self-assigned this Jan 9, 2025
@StartAutomating StartAutomating added the enhancement New feature or request label Jan 9, 2025
github-actions bot pushed a commit that referenced this issue Jan 12, 2025
feat: Get-WebSocket -Force ( Fixes #58 )
f216e42
StartAutomating pushed a commit that referenced this issue Jan 12, 2025
feat: Get-WebSocket -Force ( Fixes #58 )
4926a83 
Allowing -Force on HttpListener jobs
@StartAutomating StartAutomating added this to the WebSocket-Server milestone Jan 25, 2025
@StartAutomating StartAutomating mentioned this issue Mar 22, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@StartAutomating StartAutomating

Labels
enhancement New feature or request
Projects
None yet
Milestone
WebSocket-Server
Development

No branches or pull requests
1 participant
@StartAutomating