Hello I've found a bug on TradingView generator: it presumes that only the last order is the closing one and the others are just a long or short positions. If I have a open position and one reduce position and a third close position ...it produce two long positions and a closing one. I work on it, my question is: I found populated correctly the order flag is_reduce_only the flag is_close in the example above is always False in the three orders. I was expecting the last one had that flag to True , it should? In the third order (the closing one) the role property is CLOSE POSITION and in the second REDUCE POSITION so I can use this property to understand the purpose of the order (I would have preferred to use a boolean value but for now it could be ok)

Bug on TradingView generator (a question about is_close flag)

Gabri

Hello
I've found a bug on TradingView generator: it presumes that only the last order is the closing one and the others are just a long or short positions. If I have a open position and one reduce position and a third close position ...it produce two long positions and a closing one.
I work on it, my question is:

I found populated correctly the order flag is_reduce_only
the flag is_close in the example above is always False in the three orders. I was expecting the last one had that flag to True, it should?
In the third order (the closing one) the role property is CLOSE POSITION and in the second REDUCE POSITION so I can use this property to understand the purpose of the order (I would have preferred to use a boolean value but for now it could be ok)

Gabri

Ok, I resolved using simply side property of the order (maybe other flags seems (to me) not correctly populated like is_new).

I have another annoying issue: to reduce a bunch of chars on the output I need to understand if the order is done ad the open/closing candle time (open a market order long/short) or during a candle creation (ie: stop loss or take profit). So far I tried to understand it calculating the modulus of the timestamp divided by timeframe (in millisecs). For example in a 4h timeframe I check if the
execution timestamp % timeframe * 60000 == 0
But it is not reliable (ie: a timestamp at 16:00 can be dived by 4*60000 and the same for 18:00 that is in the middle of 4h candle).
Do you know if there is a way I can understand if a order is made at candle close/open?
Maybe all market orders (no stop nor limit) are in these conditions?
Thanks