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
Wrong extentions property type #1244
Comments
We try to emulate the browser interface but in this case I don't see a reason to use a string. get extensions () {
return Object.keys(this._extensions).join(',');
} but again I don't see any real advantage. |
I agree it's not so important for this property but in general I find it very interesting to have ws that implements Websocket as much as possible and it's already the case 👍 Making this a getter would make ws behave like the WebSocket specifications from what I know and I could remove one test here https://github.com/dcharbonnier/advanced-websocket/blob/develop/src/Waterfall.ts#L49 Was just to let you know, feel free to close it if you want. |
I see, feel free to open a PR. |
Make `extensions` a getter that returns the negotiated extensions names. Fixes #1244
Make `extensions` a getter that returns the negotiated extensions names. Fixes #1244
Make `extensions` a getter that returns the negotiated extensions names. Fixes #1244
Make `extensions` a getter that returns the negotiated extensions names. Fixes #1244
Make `extensions` a getter that returns the negotiated extensions names. Fixes #1244
The extension property of the client return an object, the websocket api expect a string.
ws/lib/WebSocket.js
Line 53 in 4e7d48a
MDN documentation
The text was updated successfully, but these errors were encountered: