scratchfoundation / scratchfoundation/scratch-blocks
Consider changing For Each block
Open
Nobody has claimed this yet.
needs discussion
request
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
While it has long been considered an obsolete block, the For Each block is still included in 3.0, and would still be very useful. I propose that we change the visual syntax of the block, as to not confuse scratchers are unfamiliar with it (should it be used in a project)
Before:
for each [variable] in (number) {
say (variable)
}
After:
repeat (number) and advance [variable] {
say (variable)
}
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 reviewing the existing For Each block described in the issue and comparing its current visual syntax with the proposed form. Done means the block uses the proposed “repeat and advance” wording without confusing Scratch users, with the behavior preserved and the rendered syntax verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100