Closed goodboy closed 2 years ago
Order "edits" now fully working ππΌ
Pretty sure everything is mostly working.
Just need to test some live clears and darks.
@iamzoltan @guilledk think this puppy is finally ready!
I've tested all live cases and we now have basic withdrawal compensation such that a position size will reflect such transactions in the accumulated size of any open position ππΌ
WS based order management with fixes for #310, #296 and hopefully most of #290.
Leverage the new 3.10
match:
syntax like crazy which turned out very nicely for making the msg loops way more grokableIncludes safeguard code to cancel all persistent orders found on startup until we get existing order loading working the EMS as per #293.
TODOs:
handle_order_updates()
{event: '[submit/edit/cancel]Orderstatus'}
blocks into a new sub-func?cryptofeed
for symbol normalization? bc kraken has a diff set for rest vs. ws apis.... (kill me)~ solved this for now using kraken's own asset info and pairs mapping tables.collections.ChainMap
to track thedict
-oriented flow of order dialogs on thekraken
api leg.Follow up (mostly pertaining to the wishlist in #345):
Position.size
logic?piker.pp
immediate file updates, some we need to implement likely with thetrio
async file IO apis.~ added to #345 and will come in a follow up PR.userref
always being0
in theopenOrders
ep to kraken here: https://support.kraken.com/hc/en-us/requests/new?ticket_form_id=96688