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
CONTEXT:
When we create a TP/SL order with the full size position it will be a POSITIONAL_TP_SL but for custom qty TP/SL the type is TP_SL.
ISSUE:
As the tp sl with a custom qty is a TP_SL type, actually usePositionStream won't show the current algo order as it is filtered inside the findPositionTPSLFromOrders function ( order.algo_type === AlgoOrderRootType.POSITIONAL_TP_SL ).
FIX:
Adding a condition to the actual findPositionTPSLFromOrders to check if (order.algo_type === AlgoOrderRootType.POSITIONAL_TP_SL) OR (order.algo_type === AlgoOrderRootType.TP_SL )
The text was updated successfully, but these errors were encountered:
Veenoway
added a commit
to Veenoway/orderly-js-sdk
that referenced
this issue
Oct 10, 2024
CONTEXT:
When we create a TP/SL order with the full size position it will be a POSITIONAL_TP_SL but for custom qty TP/SL the type is TP_SL.
ISSUE:
As the tp sl with a custom qty is a TP_SL type, actually usePositionStream won't show the current algo order as it is filtered inside the findPositionTPSLFromOrders function ( order.algo_type === AlgoOrderRootType.POSITIONAL_TP_SL ).
FIX:
Adding a condition to the actual findPositionTPSLFromOrders to check if (order.algo_type === AlgoOrderRootType.POSITIONAL_TP_SL) OR (order.algo_type === AlgoOrderRootType.TP_SL )
The text was updated successfully, but these errors were encountered: