Right now, some errors cause a panic in the websocket data parsing thread while others just keep going(ReaderDataNotFound). This behaviour doesn't allow the user to react to the errors. It simply requires a full reset of the thread but the user doesn't even know when the error occurs because it's only being logged and not sent to the user.

Could we add functionality for sending pings from the websocket manager? I see a couple ways we can do this:

1. Run an async background process that continuously sends pings every x seconds.
2. Expose a function on the WsManager struct that sends a ping whenever it is called.

Given that 1 is what the hyperliquid-python-sdk does, it is probably the best option. To make this change non-intrusive and to not change the behavior of the WS manager for everyone, we can add this behind a feature flag.

You can cancel all open orders on the exchange GUI, but I don't see this endpoint in the documentation or the sdk.

Thank you!

https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/tick-and-lot-size

Add this to the ordering to make ordering much easier without the user having to think about these things.

Would it be possible to add an option to specify own ClientOrderId for new order request? Like it is supported in python SDK.

Thanks!

It would add more data to the response and would help manage orders in applications

This should help abstract away the need to know how to create the correct the order and also handle all the errors

Could we add support for WsUserNonFundingLedgerUpdates as described in https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/websocket#wsusernonfundingledgerupdates?

I would like to use the SDK to subscribe to the hyperliquid websocket to listen for InternalTransfers but currently it looks like this functionality is not present.

There is currently no CI, so PRs can be merged with poorly formatted code, linting errors, build failures, or test failures. Add a CI that checks that all of these things must pass before merging a PR.

There is currently no documentation in https://docs.rs/hyperliquid_rust_sdk/latest/hyperliquid_rust_sdk/, which makes it hard to understand what various functions input/outputs are and what various structs are representing. We should add doc comments so that the SDK is more easy to use.

[2024-05-26T12:59:06Z ERROR hyperliquid_rust_sdk::ws::ws_manager] Error processing data received by WS manager reader: Reader data not found

Hi, i am run the cargo run --bin ws_trades but it shows this error after some minutes.
please check.thanks.