scratchfoundation / scratchfoundation/scratch-blocks
Revisit Behavior of Bump Neighbors
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
Expected Behavior
Blocks that are freshly placed on the workspace get bumped to avoid other blocks.
Actual Behavior
Sometimes a new block gets bumped such that it gets placed on top of another block.
Discussion
What is the desired behavior of bumping blocks?
See discussion in #1677 of current "weird" behavior, and the related blockly issue: google/blockly#2011
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the discussion in #1677 and the related google/blockly#2011 issue to understand the competing expectations for bumping blocks. Reproduce the reported overlap behavior in a Scratch Blocks workspace, then define and validate the desired behavior before identifying the affected implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100