-
-
Notifications
You must be signed in to change notification settings - Fork 164
Ease testing with own websocket server #304
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
Labels
enhancement
New feature or request
Comments
10 tasks
Basically, this is support for TCP Redirect right? So socks5 proxies should become supported too? |
Didn't try - I didn't have such a task. But it is quite feasible. |
I merged the PR thank you, but i removed the LOCALHOST settings. This will be included in the next relaease > 1.42.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I need to replace the exchange with my mock server so that I can test the client for a load. Since there is a lot of hardcode in the code and a lot of coupling - to do this without crutches, patching is very difficult and time consuming.
I propose to make the initialization of the manager in this regard - more flexible.
Describe the solution you'd like.
To replace the exchange with your mock server, just specify
exchange=Exchanges.LOCALHOST, exchange_type='dex'
(orcex
) when initializing the manager.exchange_type
must be specified only forLocalhost
. You can also setwebsocket_base_uri
andmax_subscriptions_per_stream
otherwise the default values will be applied.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: