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

exchanges: Add Futures WebSocket streaming and Spot WebSocket API #1446

Open
wants to merge 41 commits into
base: master
Choose a base branch
from

Conversation

samuael
Copy link
Contributor

@samuael samuael commented Jan 14, 2024

Selam team

This pull request introduces the WebSocket streaming functionalities for futures and API endpoint call methods through the Websocket stream for spot endpoints. The future web socket streaming adds support for USDTMarginedFutures and CoinMarginedFutures assets. It establishes connections and handles incoming stream data separately. Furthermore, the pull request extends support for SPOT WebSocket API and API endpoint calls via a distinct WebSocket stream. Ultimately, these WebSocket endpoint calls are seamlessly integrated with the wrapper functions.

Fixes # (issue)

Type of change

Please delete options that are not relevant and add an x in [] as the item is complete.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How has this been tested

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration and
also consider improving test coverage whilst working on a certain feature or package.

  • go test ./... -race
  • golangci-lint run
  • Test X

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation and regenerated documentation via the documentation tool
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally and on Github Actions with my changes
  • Any dependent changes have been merged and published in downstream modules

@gloriousCode gloriousCode added review me This pull request is ready for review builds require fixing labels Jan 14, 2024
Copy link
Collaborator

@shazbert shazbert left a comment

Choose a reason for hiding this comment

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

linter and spell checker needs to be fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants