-
-
Notifications
You must be signed in to change notification settings - Fork 75
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.
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
Add #injectWS #276
Add #injectWS #276
Conversation
Now is possible to invoke an websocket handler without listening
Can I have some CI love? on my MacOS latest with node 20 it is passing |
Added testing paragraph
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
The user must manually close the ws in the test
It allows to enhance the request made for upgrading the socket
Implementation as close as possibile to ws connectiong error
Can someone approve the workflow to run? |
Seems CI is failing |
I am waiting for mafintosh/stream-shift#6 to be solved. |
I can see that the issue linked has no activity, I will change my implementation to use mock-socket as @airhorns suggested. |
mafintosh/stream-shift#6 looks solved. I ran all the tests locally for node 21. The pipeline now should pass. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Is there something I can do to make this mergeable? |
Nothing, me shipping it! |
Now is possible to invoke an websocket handler without listening.
closes #35
Checklist
npm run test
andnpm run benchmark
and the Code of conduct