Add containment support to shuffle - #24
Merged
Merged
Conversation
smoores-dev
force-pushed
the
shuffle/containment
branch
from
May 19, 2026 16:11
7b42573 to
38507c4
Compare
smoores-dev
force-pushed
the
shuffle/containment
branch
from
May 19, 2026 16:19
38507c4 to
7ed71b1
Compare
pdiffley
pushed a commit
that referenced
this pull request
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Containment allows for consumers to specify that a given node type shouldn't ever be allowed to be dragged out of a ancestor with the specified node type. I added an example to the demo. The idea is to prevent, e.g., a Card node type from being dragged from one Card Deck node to another Card Deck node, instead restricting each Card to being dragged around within its nearest Card Deck.