theotherdavid / kraken-meta-order Goto Github PK

Currently, we're storing the orders themselves, but not the prices. Because orders like SL/TP can have multiple prices, we should make this a separate table with an FK to META_ORDER.

We need a way to look up all active orders. So we should add status=ACTIVE as a query parameter, and then have the SQL query apply that in the WHERE clause.

Pass in an ID, get the order out of the system.
This should be a GET request.

Integrate with their API and get the price for a certain coin (currency pair?). For now, just return the response to the API.

I guess this could be a DELETE method.
But we don't actually "DELETE" anything, of course. We would set it to CANCELLED.

Implement Create Meta-Order endpoint, taking in a JSON object and persisting it in the DB.

Request:
{
"metaOrderId": null,
"metaOrderType": enum (currently only STOP_LOSS_TAKE_PROFIT)
"status": enum (ACTIVE, COMPLETED, CANCELLED, ERROR)
"stopLossTakeProfit": {
"stopLossPrice": double,
"takeProfitPrice": double
}
}

This should be a GET request.
I think by default we should only return inactive, but have an option to include COMPLETED records too.

Currently, the database is wiped and recreated every time we start the app. This isn't ideal. I think Volumes are the way to persist data outside the container.