## don't do without consider

- we do not release on open **useSortableContainer** hook. Because we need to pass `containerInfo` to **useSortableElement** , we do it by context provider. we can do same thing with give `containerInfo` to app devoleper's they will send it to **useSortableElement**, in this case the problem is if they put two sortable container as parent chlid, But they mix `containerInfo` to **useSortableElement** something like first sortable as parent,second sortable as child, third sortable as parent ...etc, we will not do anythig our sortable will collabse, So we do not release on open **useSortableContainer** hook.
- `isMarginMerged` was not supported because , it does not want as required , make all UI without that. with flex.

### Just My thought some strikes ( you can ignore it)

**NOTE**:-
isMarginMerged was not supported because , it does not want as required , make all UI without that .

**NOTE**:-
we have able to make as current sortable element always height :0 and width:0 , or display :none

**NOTE**:
in sortable in sortstart the sorting element (which element want to be a sorting or which elements position want to be change) do not make it as display none , Because in fire fox dragenter called but drag leave does not triggered
To solve this 1. do not make sorting element as display none 2. use sorting element as DropShadow ( the placeholder in droppable (drop zone) )

**v2**
feature request form mahesh anna
drag Image in react.portal because if they handle that it will be colllapsed

I have doubt with drag and drop state change,
**Doubt** :-
we want to give some custom event or original event listening process for extra customazation
`Option 1`: we can expose original events
`Option 2`: we can listen store (state) change and expose listener method what our users could want
`Option 3`: now we give some customazation and veriyasly we could choose "Option 1" or "Option 2"

        currently i choose Option 2 ,Because it was easy

// issue in @zohodesk/react-dnd if element removed in Drop are before onDragEnd is not triggered

need to check in react-dnd
Reason ;-

// issue in @zohodesk/react-dnd if element removed in Drop are before onDragEnd is not triggered

Because if element is not in dom then we trigger dragend is right
.next , we can solve this with if component disconnect call we first check is dragEnd is called then we remove listener
if drag end is not called then in the end of Drag ent we will remove the listener
