Implement options passing to websocket constructor#157
Closed
jazarja wants to merge 2 commits intobinance:masterfrom
Closed
Implement options passing to websocket constructor#157jazarja wants to merge 2 commits intobinance:masterfrom
jazarja wants to merge 2 commits intobinance:masterfrom
Conversation
Contributor
|
Hey @jazarja , we published a new modularised version of the TS connector that has a proxy configuration websockets. You can find more details on the migration guide. |
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
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.
Websocket currently does not have built-in support for proxy configurations. Consequently, it's necessary to provide necessary options directly to the WebSocket constructor when establishing a connection.
Example: