You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently can't be swapped over easily to MktPair bc we don't
relay enough info through the clearing sys msg set to reproduce
via the new `.from_fqme() method..
probably best solution is to instead require all backend's to
provide the MktPair msg directly as part of loading pre-existing
live dialogs?
we should probably consider making a Cascade msg-type which
describes IO for cascaded Flumes? Probably something to get into
when we get back to formalizing that subsys XD
Lingering task(s) from #489 that we couldn't quite wrap up due to,
the
Symbol
usage in.ui.order_mode
:OrderMode.load_unknown_dialog_from_msg()
https://github.com/pikers/piker/blob/master/piker/ui/order_mode.py#L641
MktPair
bc we don'trelay enough info through the clearing sys msg set to reproduce
via the new `.from_fqme() method..
provide the
MktPair
msg directly as part of loading pre-existinglive dialogs?
order_mode
further UX refinement ideas needing feedback #220deribit
backend is still missingAsset
usage inMktPair
s andi only wasn't able to due this due to having no account set up to get
the data APIs..
there's a hacky shim-usage of
MktPair
for the fsp flumes inui._fsp
: https://github.com/pikers/piker/blob/rekt_pps/piker/ui/_fsp.py#L493Cascade
msg-type whichdescribes IO for cascaded
Flume
s? Probably something to get intowhen we get back to formalizing that subsys XD
Editting initial live order load fails? #502 seems to be related to this as well?
The text was updated successfully, but these errors were encountered: