feat(subscription/l2Book): add optional 'fast' field#142
Conversation
|
Is there anything we can do to help move this forward? We are building on top of this and are keen to adopt the Let us know if there's anything we can do to get this over the finish line! |
…request field - Add `fast?: true` to `L2BookEvent` for snapshots pushed in fast mode - Change the request field from `v.nullish(v.boolean(), false)` to `v.optional(v.boolean())`, omitting `fast` when unset instead of sending `false` - Fix the field JSDoc that was written as a `//` line comment instead of `/**` - Drop the server-rejected `fast: null` test case
|
I pushed a few changes on top before merging:
Thanks for your contribution! |
|
@gambinish, I was planning to ship the release within 1-2 days (I need to write up all the changes in the new version + double-check that the current API schemas/types are still accurate). |
Thank you! We're going to go ahead and integrate this now. Appreciate your effort here. |
What & why
Add the optional 'fast' field in the websocket subscription schema of L2BookRequest.
The field changes the manner in which the responses are pushed("5 levels if fast, 20 levels if slow")->docs (search for l2Book)
Via telegram Hyperliquid API Announcements(@hyperliquid_api) :
5 seconds" (https://t.me/hyperliquid_api/326).Type of change