Releases: JKorf/BitMEX.Net
Releases · JKorf/BitMEX.Net
BitMEX.Net Version 2.7.0
- Updated CryptoExchange.Net version to 9.7.0, see https://github.com/JKorf/CryptoExchange.Net/releases/
- HTTP REST requests will now use HTTP version 2.0 by default
BitMEX.Net Version 2.6.0
- Updated CryptoExchange.Net version to 9.6.0, see https://github.com/JKorf/CryptoExchange.Net/releases/
- Added ClearUserClients method to user client provider
BitMEX.Net Version 2.5.1
- Added Invalid API key error parsing
- Added unknown symbol websocket error mapping
BitMEX.Net Version 2.5.0
- Updated CryptoExchange.Net to version 9.5.0, see https://github.com/JKorf/CryptoExchange.Net/releases/
- Added improved error parsing
- Added additional success check on restClient.ExchangeApi.Trading.CancelOrderAsync endpoint
- Updated rest request sending too prevent duplicate parameter serialization
Updates notes:
- Error.Code is deprecated, use Error.ErrorCode instead for checking specific errors
BitMEX.Net Version 2.4.0
- Updated CryptoExchange.Net to version 9.4.0, see https://github.com/JKorf/CryptoExchange.Net/releases/
- Added support for multi-symbol Shared socket subscriptions
BitMEX.Net Version 2.3.0
- Updated CryptoExchange.Net to version 9.3.0, see https://github.com/JKorf/CryptoExchange.Net/releases/
- Updated websocket message matching
BitMEX.Net Version 2.2.1
- Updated CryptoExchange.Net to version 9.2.1, see https://github.com/JKorf/CryptoExchange.Net/releases/
- Fixed issue with websocket ping response parsing
BitMEX.Net Version 2.2.0
- Updated CryptoExchange.Net to version 9.2.0, see https://github.com/JKorf/CryptoExchange.Net/releases/
- Removed some fields from restClient.ExchangeApi.Account.GetAccountInfoAsync response model no longer returned by API
Version 2.1.0
- Updated CryptoExchange.Net to version 9.1.0, see https://github.com/JKorf/CryptoExchange.Net/releases/
- Added (I)BitMEXUserClientProvider allowing for easy client management when handling multiple users
Version 2.0.0
- Updated CryptoExchange.Net to version 9.0.0, see https://github.com/JKorf/CryptoExchange.Net/releases/
- Added support for Native AOT compilation
- Added RateLimitUpdated event
- Added SharedSymbol response property to all Shared interfaces response models returning a symbol name
- Added GenerateClientOrderId method to ExchangeApi Shared clients
- Added OptionalExchangeParameters and Supported properties to EndpointOptions
- Added IBookTickerRestClient implementation to ExchangeApi Shared client
- Added ISpotOrderClientIdClient implementation to ExchangeApi Shared client
- Added IFuturesOrderClientIdClient implementation to ExchangeApi Shared client
- Added ISpotTriggerOrderRestClient implementation to ExchangeApi Shared client
- Added IFuturesTpSlClient implementation to ExchangeApi Shared client
- Added TriggerPrice, IsTriggerOrder and IsCloseOrder to SharedFuturesOrder model
- Added TriggerPrice and IsTriggerOrder properties to SharedSpotOrder response model
- Added QuoteVolume property mapping to SharedSpotTicker response model
- Added All property to retrieve all available environment on BitMEXEnvironment
- Added automatic mapping between XBT and BTC asset and symbol names when using the Shared implementations
- Added missing Enum value ExecutionType enum
- Refactored Shared clients quantity parameters and responses to use SharedQuantity
- Updated all IEnumerable response and model types to array response types
- Updated ExecutionInstruction property on BitMEXOrder model to array
- Renamed BitMEXExchangeSymbolOrderBook to BitMEXSymbolOrderBook
- Removed Newtonsoft.Json dependency
- Removed legacy AddBitMEX(restOptions, socketOptions) DI overload
- Fixed incorrect DataTradeMode on certain Shared interface responses
- Fixed InvalidOperationException on empty socket user snapshot updates
- Fixed some typos
- Fixed error using Shared GetAssetsAsync endpoint
Updates notes:
- Processing responses which previously returned an IEnumerable now return an array. Although you can still call
ToList
orToArray
this overhead can now be removed - The
AddBitMEX(restOptions, socketOptions)
overload was removed but can be replaced byAddBitMEX(options)
, whereoptions.Rest
is the same as the previous versionsrestOptions
andoptions.Socket
is the same as previous versionssocketOptions
. - When providing quantities for the Shared interfaces you now need to specify the type of quantity:
SharedQuantity.Base(/*qty*/)
,SharedQuantity.Quote(/*qty*/)
orSharedQuantity.Contracts(/*qty*/)
. - Quantity responses for the Shared interfaces have the same logic, quantities are wrapped in the
SharedOrderQuantity
model, containing theQuantityInBaseAsset
,QuantityInQuoteAsset
andQuantityInContracts
properties. - See https://cryptoexchange.jkorf.dev/client-libs/shared/quantities for more info on the new quantity notations
- Structured logging SourceContext now include the client type, previously the SourceContext was always
BitMEX
, it is now splitBitMEX.RestClient
andBitMEX.SocketClient
. Update any logic depending on this accordingly. - AssetAlias configuration has been added. When using Shared interfaces automatic mapping is enabled between
XBT
andBTC
. To prevent this entirely useBitMEXExchange.AssetAliases.AutoConvertEnabled = false;
. Previously the mapping was being applied inconsistently.