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
go-binance/service_websocket.go
Line 344 in c656b55
tag 't' used twice in same structure.
./service_websocket.go:344: struct field TakerCommision repeats json tag "t" also at ./service_websocket.go:342
according to https://github.com/binance-exchange/binance-official-api-docs/blob/master/user-data-stream_CN.md
rawAccount := struct { Type string `json:"e"` Time float64 `json:"E"`
// remove this -> //OpenTime float64 json:"t" MakerCommision int64 json:"m" TakerCommision int64 json:"t" BuyerCommision int64 json:"b" SellerCommision int64 json:"s" CanTrade bool json:"T" CanWithdraw bool json:"W" CanDeposit bool json:"D" Uptime float64 json:"u" // <------------ add this Balances []struct {
json:"t"
json:"m"
json:"b"
json:"s"
json:"T"
json:"W"
json:"D"
json:"u"
The text was updated successfully, but these errors were encountered:
I support this repo here: https://github.com/filinvadim/go-binance
Sorry, something went wrong.
No branches or pull requests
go-binance/service_websocket.go
Line 344 in c656b55
tag 't' used twice in same structure.
./service_websocket.go:344: struct field TakerCommision repeats json tag "t" also at ./service_websocket.go:342
according to https://github.com/binance-exchange/binance-official-api-docs/blob/master/user-data-stream_CN.md
// remove this -> //OpenTime float64
json:"t"
MakerCommision int64
json:"m"
TakerCommision int64
json:"t"
BuyerCommision int64
json:"b"
SellerCommision int64
json:"s"
CanTrade bool
json:"T"
CanWithdraw bool
json:"W"
CanDeposit bool
json:"D"
Uptime float64
json:"u"
// <------------ add thisBalances []struct {
The text was updated successfully, but these errors were encountered: