microsoft / microsoft/pxt-microbit
Rule list design suggestions
Open
Nobody has claimed this yet.
code eval tool
- Dominant language
- TypeScript
- Stars
- 804
- Forks
- 721
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 2
Description
Might be nice to be able to re-order (move up or down) the rules in a list.
Also, could we use a numbered list? I just remember that teacher who made his students reference the rule number in their programs.
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
No file or test is named. Start by locating the rule-list UI in the TypeScript editor, then inspect how rules are rendered and updated. Done means users can move rules up or down and each rule is displayed with a number.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100