Open Felienne opened 7 months ago
Hi! That's a great idea. I think since I have prior experience with Skulpt I might take this one.
Just want to point out that during the previous contributors meeting we were discussing this issue and @hasan-sh expressed interest in picking it up.
It seems that now the code sample produces a nice error but I was able to find another program with a leaking error (logged as #5322):
time is 10
forward time
Just want to point out that during the previous contributors meeting we were discussing this issue and @hasan-sh expressed interest in picking it up.
It seems that now the code sample produces a nice error but I was able to find another program with a leaking error (logged as #5322):
time is 10 forward time
True Boryana, i remember having an idea that'd possibly be the solution. That is, we could add a wrapper for errors (error boundary component!) where we catch all sorts of errors and perhaps only show a generic message when a "python error" is returned from the backend. I'm not sure about the validity of this proposal, but i guess it'd be nice to work with skulpt and find out?! :)
Also while working on https://github.com/hedyorg/hedy/pull/4677 I noticed again we have ugly error messages of Python leaking out:
Why don't we add a catch all on the front-end and show the "you write a program we were not expecting" error that we alreayd have for hard back-end errors.
It surely looks nicer! (Although it will make debugging harder for us, that's ok)
I suspect this is easy to do for a front-ender (like @jpelay or @hasan-sh?).