We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello. Is there a reason why there are some critical attributes on Futures API that are optional?
Example: https://github.com/gateio/gateapi-nodejs/blob/master/model/futuresOrderBookItem.ts
In the FuturesOrderBookItem, p for price and s for size are both optional, even tho they are both always present.
FuturesOrderBookItem
p
s
Another example is the FuturesOrderBook itself: https://github.com/gateio/gateapi-nodejs/blob/master/model/futuresOrderBook.ts
FuturesOrderBook
current and update - as I can see from the documentation - are always present.
current
update
Thanks in advance =)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello. Is there a reason why there are some critical attributes on Futures API that are optional?
Example: https://github.com/gateio/gateapi-nodejs/blob/master/model/futuresOrderBookItem.ts
In the
FuturesOrderBookItem
,p
for price ands
for size are both optional, even tho they are both always present.Another example is the
FuturesOrderBook
itself: https://github.com/gateio/gateapi-nodejs/blob/master/model/futuresOrderBook.tscurrent
andupdate
- as I can see from the documentation - are always present.Thanks in advance =)
The text was updated successfully, but these errors were encountered: