Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors not being propagated upwards into editor #532

Closed
StoneCypher opened this issue Jan 14, 2021 · 3 comments
Closed

Errors not being propagated upwards into editor #532

StoneCypher opened this issue Jan 14, 2021 · 3 comments

Comments

@StoneCypher
Copy link
Owner

The reason #531 required Christopher to reach out to me is that the engine was saying Uncaught Error: already has "a" to "b", but the editor wasn't catching it

As a result, Christopher couldn't tell what was actually wrong

Fix this

@blackeuler
Copy link

Hmm I wasn't sure if not propagating the error was a design choice, users shouldn't be concerned with Console Errors. This did make it at least seem like on the surface an intended feature instead of a crash.

@StoneCypher
Copy link
Owner Author

it's not a console error. the machine is throwing because the code is wrong (by design)

the editor absolutely should be picking it up

image

@StoneCypher
Copy link
Owner Author

Re-check this while you're at it

#343

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants