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
Is your feature request related to a problem? Please describe.
I'd like to know more easily when a trade is going to be closed due to minimal_roi dict. Currently, all I can do is to check open time and manually compute next potential close date.
Describe the solution you'd like
In trade detail pane, I'd like to have a line showing the next minimal_roi dict entry (it's estimated sell date) and probably put it in red or green depending on if the ROI is reached.
That's correct, you won't be able to handle this in freqUI alone.
I'm also not sure it's straightforward in freqtrade itself - as the ROI method is not meant to be used that way.
I'm however also doubting the sense of having this, as it'll only serve a limited set of strategies.
It might be helpful if you rely on min_roi - but the moment your strategy uses one of the advanced features (custom_sell, custom_stop), trailing stoploss, it'll not really give you much help - as we can't know when custom_sell triggers - as the logic there can be anything.
Is your feature request related to a problem? Please describe.
I'd like to know more easily when a trade is going to be closed due to
minimal_roi
dict. Currently, all I can do is to check open time and manually compute next potential close date.Describe the solution you'd like
In trade detail pane, I'd like to have a line showing the next
minimal_roi
dict entry (it's estimated sell date) and probably put it in red or green depending on if the ROI is reached.Describe alternatives you've considered
Additional context
I'd be happy to try to do it myself but I don't have much background in vue.
I saw mainly this view to be updated: https://github.com/freqtrade/frequi/blob/master/src/components/ftbot/TradeDetail.vue (alongside trades.ts file) but I guess computations should be done in the main repo (rpc.py file)?
King regards,
Maxime
The text was updated successfully, but these errors were encountered: