Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

while moving between two lists only first nestable maxDepth is considered #93

Open
unikumspace opened this issue Nov 16, 2017 · 0 comments
Labels

Comments

@unikumspace
Copy link

Expected behavior

Situation: having 2 lists with different maxDepth values, trying to move items from first list to second.
see template

It should be impossible to move "Second item" with its children from first list to "First item" of second, because second nestable depth will be more than defined in maxDepth property.

It should be possible to move "Second item" from second list inside "First item" of first list. Resulting total depth would be 3, which is in correspondence with first nestable maxDepth property.

Actual behavior

It's possible to move "Second item" with its children from first list to "First item" of second, even though second list has a maxDepth of 2 and movable item itself has a depth of 3.

Also "Second item" from second list can't be moved inside "First item" of first list, even though first list has a maxDepth of 3 and such move should be legitimate.

It seems that only maxDepth of first nestable (which was moved from) is taken in count. If movable item has children - their depth should also be considered (total depth = movable item depth + movable item children depth). Otherwise it becomes possible to move items into other nestables, resulting in its total depth over the limit defined by maxDepth property.

@pjona pjona added the bug label Nov 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants