@andrelcgt The connectivity was designed to be minimal - minimal handling to ensure the request goes through and minimal post processing when a response arrives, giving it back to the user as is. This leads to extremely predictable behaviour without any library-specific weirdness, since these responses are passed back to you exactly as the exchange gave them. Even this difference between Bybit's WebSocket API & REST API responses is actually coming from Bybit.

For the most part, by accepting request parameters and returning responses exactly as described in the exchange's API docs, it's easier for anyone working with the api docs as reference. So each API client is an exact match to the corresponding API docs from that exchange. Simpler integration, less risk for user error/confusion, a more predictable experience over all.

That being said, what you said makes a lot of sense to me too - I do eventually want to release a simpler interface though that unifies how we interact with different exchanges. This per-exchange/product integration forces additional normalisation effort because, as you said, the same parameters have different names or even the values are differently presented (binance likes to receive & send numbers as strings). I'm still undecided how to approach this.

Idea 1: I definitely won't change the return types of existing REST & WS API clients - that's a heavy breaking change, additional complexity for new adopters, and a nightmare with the return types of each method.

Idea 2: A flag to enable normalised responses would be nice, but there's still the question on how to cleanly type the return values of each function when that flag is enabled. Might be feasible though... needs some R&D.

Idea 3: Alternatively I could introduce a NormalisedRESTAPI (name could be improved) client to each SDK, which wraps around the existing API clients and normalises requests/responses into a singular standard. This would keep the complexity away from the existing API clients, but it would introduce a lot of duplicate code (each endpoint would have a standard and a normalised method). It would be more predictable but unsure about this vs idea 2.

Eventually, I'd love for each SDK to include a normalised way of communicating with each exchange & product group in a standardised way, so any system can easily switch between exchanges (bybit & binance) or different product groups within that exchange (spot/margin/linear/inverse futures etc) with minimal integration overhead. It's been on my mind for a while - if you have other ideas to add here, I'd love to hear them!

Uh oh!

Config setting to throw REST exceptions #437

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions