microsoft / microsoft/pxt-microbit
Error is still rendered even when a block is not active
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 804
- Forks
- 721
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 2
Description
There was a block that was giving me an error, so I removed it from the active code. Even though the block will be ignored and does not show up in the error pane, the error state of the block is still rendered. This makes me feel like there is an error still in my code.
To Reproduce
Steps to reproduce the behavior:
- Go to beta or live
- Open a project
- Add a block that will error to blocks that will run, like adding show image to an on start or another input block
- Pull the block out into the workspace
- See that even though the block is grayed out, the error state is still showing on the block
Expected behavior
When I pull a block out and it is no longer executing, the error state of the block should go away.
Desktop (please complete the following information):
- OS: Windows 11
- Browser: Firefox
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
Reproduce the issue in the beta or live editor by adding an erroring block, pulling it out of the running workspace, and checking the block and error pane. Start by tracing how the workspace marks inactive blocks and renders their error state. Done means the grayed-out, non-executing block no longer displays an error state while active errors remain visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100