Closed bennuttall closed 8 years ago
Thanks for this! Working on making the errors more visible via an indicator in the file tab that has the error. Also, in the example you gave a bug was preventing that import statement from being highlighted in red like a normal error, and that'll be fixed next deploy. Between the two there should be a lot more going on above the fold. We also likely should make the demo iframe a little smaller so more of it is visible on more screens.
@bennuttall thanks again for finding this. This is now fixed! There is a Red icon in the tab of the error and the line is highlighted.
In Epiphany and other browsers where we've disabled Ace, the line number of the error will turn red.
Closing as fixed, but feel free to drop further feedback here.
I've discovered that this still happens if the error is not caused by bad syntax, for example an incorrect parameter type:
from sense_hat import SenseHat
sense = SenseHat()
sense.set_rotation(75)
Nice find. Looking into this.
@davidhoness Fixed! Thanks again for finding this.
On my laptop (1600x900 resolution), the error message is shown off screen, and there's no indication that an error has occurred:
Scrolled down:
If the error could pop up or the editor went red, or the error line was highlighted, anything that would indicate there's an issue would be really helpful.