Skip to content
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

fix GetFullOrderBookWebSocketAsync data inconsistency #714

Merged
merged 1 commit into from
Jan 10, 2022
Merged

fix GetFullOrderBookWebSocketAsync data inconsistency #714

merged 1 commit into from
Jan 10, 2022

Conversation

BZ-CO
Copy link
Contributor

@BZ-CO BZ-CO commented Jan 10, 2022

Proposal for removing maxCount parameter from ParseOrderBookFromJTokenArrays and ParseOrderBookFromJTokenDictionaries.
Currently we are trimming the incoming order book data before processing it, which seems wrong and causes order book inconsistency as mentioned in #713 .
Instead I propose moving maxCount trimming logic to GetFullOrderBookWebSocketAsync, because that's the method responsible for order book data store as well.

Proposal for removing maxCount parameter from ParseOrderBookFromJTokenArrays and ParseOrderBookFromJTokenDictionaries.
Currently we are trimming the incoming order book data before processing it, which seems wrong and causes order book inconsistency as mentioned in #713 .
Instead I propose moving maxCount trimming logic to GetFullOrderBookWebSocketAsync, because that's the method responsible for order book data store as well.
Copy link
Collaborator

@jjxtra jjxtra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this refactor, much cleaner

@vslee vslee merged commit 855600f into DigitalRuby:master Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants