-
Notifications
You must be signed in to change notification settings - Fork 661
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
Refactor data request interfaces into messages #2260
base: develop
Are you sure you want to change the base?
Conversation
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.
Thanks for your work here @faysou
I think this is a great improvement:
- Better symmetry with command messages on the execution side
- Stronger contract, as request commands must be valid when initialized in
Actor
- Reduces the surface area of the
DataClient
interface, making them easier to work with
It's also a good sign that even with all the additional message types, there is still more code being removed here than added.
I think there is some change risk for the adapter clients, as test coverage isn't as strong there as the core of the system. I've reviewed them, but it would be great if we could get additional reviews when possible 🙏 :
- @sunlei for Bybit
- @davidsblom for dYdX
LGTM (dYdX changes) |
LGTM (Bybit) |
Thank you @davidsblom and @sunlei After we resolve some of the comments above, I'm planning to merge this after the next release (which should be this week). |
I'm done with the fixes. I had intended to work on doing the same for the subscribe side, but not sure it's really needed, there are less parameters and variability compared to data requests (also I don't want to embark on refactoring thousands of lines again straight away) |
Pull Request
Refactor data interfaces into messages
Type of change
How has this change been tested?
Updated existing tests