server/{auth,db}: add order_status route #687
Conversation
|
Will get on this today 100%, just a little delayed with a different fix. I'm note sure we care too much about order_status and match_status being limited to the owning user though. |
There was a problem hiding this comment.
Partial review, will return to this shortly. We may need to consider queries for cancel orders too. Alternatively, client could check the status of the targeted order instead and assume the cancel order that they are interested in was the one that matched it.
|
|
|
I think we can move forward without cancel order status support at least initially. Discussion in #687 |
Plan is to put that up after this gets merged, while #677 is reviewed. That way, I can include this new route and the update to the connect response. |
Similar in implementation to the match_status route, the order_status route
accepts a slice of `struct{Base,Quote,OrderID}` and returns the status and
fill amts for the requested **user-submitted** orders that are found in db.
Will follow up with spec changes.
itswisdomagain
force-pushed
the
order_status
branch
from
92db6eb
to
0012cf0
Compare
itswisdomagain
force-pushed
the
order_status
branch
from
0012cf0
to
6afd7bd
Compare
Similar in implementation to the match_status route, the order_status route
accepts a slice of
struct{Base,Quote,OrderID}and returns the status andfill amts for the requested user-submitted orders that are found in db.
Will put up a follow up with spec changes for the new
order_statusrouteand the updated
connectroute.