React-dnd: Nested drop targets and canDrop

I came here initially because I had the opposite problem... which I solved with monitor.isOver({ shallow: true }) in the canDrop method of both parent and child. I wanted only the child to respond, but found the parent returning false prevented the child from returning true.

Thus I think the behaviour you're describing should be the default behaviour. I'm assuming both accept the same drop types, and that your actual dom elements don't have some wierd stacking issue going on, and that your canDrop isn't getting in the way.

Anyway, I'm not a contributor/collaborator, and just found your issue by chance. You may wish to post a sandbox of your issue, as this always helps library maintainers understand exactly your problem.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@danielrob how did you solve your problem with {shallow: true} ? I'm trying to use that in canDrop and it seems to have no effect. Ideally I would want the children to have priority when dropping, and then the parents.