scratchfoundation / scratchfoundation/scratch-blocks
Procedures: should string and number argument types be combined?
Open
Nobody has claimed this yet.
custom procedures
needs-discussion
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
In Scratch 2.0 procedure arguments can be strings (%s), numbers (%n), or booleans (%b).
The current spec for Scratch 3.0 combines strings and numbers.
Advantages:
- rendering is the same for both
- implementation is slightly simpler
Disadvantages:
- Can't indicate to a user what should be attached
- Can't force the number pad to show up on mobile for number arguments
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
Review the current Scratch 3.0 procedure argument specification and compare it with the Scratch 2.0 string, number, and boolean types described here. Evaluate the rendering, implementation, user guidance, and mobile number-pad tradeoffs. Done would require a decided direction for whether strings and numbers remain combined or become distinct, along with the affected specification or implementation areas.
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
- Needs clarification
- Newbie friendliness
- 25/100