closed_trades and sl attribute

[msloco]

It seems that under some conditions (that is when a trade is closed for hitting a sl) the very .sl property of the closed_trade item corresponding to the original closed trade is set to None.
I am trying to add info to closed trades in as far as the reason they got closed (strategy, tp, sl) - which i think is somehow useful when dealing with complex strategies, and I was trying to manipulate the closed_trades adding some attributes, but I noticed this strange behavior.
Is there a possible explanation ?
cheers

[kernc]

Is there a possible explanation ?

I suspect, since Trade.sl and .tp are computed properties that depend on the underlying contingent order:

backtesting.py/backtesting/backtesting.py

Lines 657 to 666 in 8c13d00

	@property
	def sl(self):
	"""
	Stop-loss price at which to close the trade.
	This variable is writable. By assigning it a new price value,
	you create or modify the existing SL order.
	By assigning it `None`, you cancel it.
	"""
	return self.__sl_order and self.__sl_order.stop

The properties are set to None here when the trade is closed:

backtesting.py/backtesting/backtesting.py

Lines 984 to 988 in 8c13d00

	# ... by closing a reduced copy of it
	close_trade = trade._copy(size=-size, sl_order=None, tp_order=None)
	self.trades.append(close_trade)
	self._close_trade(close_trade, price, time_index)

Please confirm.

[msloco]

now, from what I see from the debugging session I setup:

it led me to see that beginning with this call trace:

next->_process_orders->if stop_price: -> order._replace(stop_price=None)

at this point the order in question is contingent and has not "sl" property by itself. though the referred "parent trade" correctly has.
but, within the order._replace, the parent trade loses its stop, resulting to be set to "None". Consequently, upon closing, the trade.sl is already None - although I am not sure how the properties propagate from order to trade.

thanks for further clarification on this point