03-27-2018, 11:46 AM
I am loving this post! The killGekko call is terrible, don't use it (it just unregisters the gekko, it will actually still be running).
In order to properly kill a gekko we need to better manage running Gekkos, I am working on a module that does that as we speak (since it will also control update events flowing from live gekkos into the UI over websocket).
However I wasn't planning on including backtests here, killing a backtest basically means aborting it (since you won't get any results, which only come at the end). Is that acceptable? If it is I can allow for the killing of those as well.
> 3. Major kill-switch; killGekko({ category: 'all' })
This will most definitely be included.
-----
Note that I am changing this as part of 0.6 which will take a while because it includes a ton of changes. But I don't see the point of doing this now with the outdated (cp.js) event flow and than redoing it with the new events.
In order to properly kill a gekko we need to better manage running Gekkos, I am working on a module that does that as we speak (since it will also control update events flowing from live gekkos into the UI over websocket).
However I wasn't planning on including backtests here, killing a backtest basically means aborting it (since you won't get any results, which only come at the end). Is that acceptable? If it is I can allow for the killing of those as well.
> 3. Major kill-switch; killGekko({ category: 'all' })
This will most definitely be included.
-----
Note that I am changing this as part of 0.6 which will take a while because it includes a ton of changes. But I don't see the point of doing this now with the outdated (cp.js) event flow and than redoing it with the new events.