Add options for constrain by each axis

[ChugunovRoman]

Related #305

[isaacHagoel]

So what's the usecase here? should the element be allowed to leave the origin dropzone?
How is keyboard dragging affected?
How is highlighting potential drop targets affected?

[ChugunovRoman]

@isaacHagoel

So what's the usecase here?

For example, I use this changes for tab swap by mouse and tabs should be moving only by X coordinate.
Also this feature can be applied in a board for constrain swap columns by Y.
And etc.

should the element be allowed to leave the origin dropzone?

What does this question related to the functionality of constraiting the movement of an element along the axes by dragging with the mouse?
I think that the functionality to allow the element to leave the dropzone is a separate feature that can be implemented if necessary.

How is keyboard dragging affected?

This has no affect on keyboard dragging. The behavior of keyboard dragging does not changed.

How is highlighting potential drop targets affected?

On highlighting potential drop targets this does not affect too.

[isaacHagoel]

I'll try to explain my concern better. Let's say I have 4 dropzones of the same type organized this way:
U
L. R
D
If you limit L to the X axis that means that elements can only be moved to R if you are using the mouse/touch but anywhere if you use the keyboard.
Also, when lifting an element from L all dropzones will be highlighted indicating that they are drop targets when in fact they are not. Same issue with the aria messages.
If L happens to be a vertical list, it also means that the items cannot be re-sorted and if R is vertical it means that any element taken from L and moved to R has only one index it can be dropped into.
This doesn't feel like good DX or UX to me. I am open to such feature, generally speaking but it needs to be thought out.

[ChugunovRoman]

I think I understood. Are you talking about the behavior of the element that was dragged out of the dragzone? I think we also able to change this behavior via new property in the options.

[segovo]

This feature works great for me, I'd just like to add that changing createDraggedElementFrom() should be considered so that if centreDraggedOnCursor is true it doesn't move the element in one of the constrained axises. In other words, centreDraggedOnCursor should only center an item vertically in a vertical only movement constrained list.

[isaacHagoel]

good point. There are many considerations and every new feature has to work in harmony with what came before. I am glad it's working great for you but I can't merge it in this way.

…

On Sat, Feb 11, 2023 at 6:41 AM Segovo ***@***.***> wrote: This feature works great for me, I'd just like to add that changing createDraggedElementFrom() should be considered so that if centreDraggedOnCursor is true it doesn't move the element in one of the constrained axises. In other words, centreDraggedOnCursor should only center an item vertically in a vertical only movement constrained list. — Reply to this email directly, view it on GitHub <#429 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE4OZC5FK3VNLFC7MXAIKJ3WW2KX3ANCNFSM6AAAAAAUOCULL4> . You are receiving this because you were mentioned.Message ID: ***@***.***>