You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Error log found here: https://pastebin.com/y81gSVYP
When the extension is attempting to read and process an expression, any time the expression is incomplete it will throw this error. It appears to "jump the gun", trying to evaluate/cast empty space.
To Reproduce
Steps to reproduce the behavior:
Create an expression. debug.Notification("Old Value: ")
Edit the expression with additional information. debug.Notification("Old Value: " +)
Error appears at this point while typing.
The text was updated successfully, but these errors were encountered:
I think this is ideal. This happens to all languages for me. When you leave a plus sign without something after it, it gives an error but the error disappears when I complete something after it.
What languages are you looking at? Generally it would be the job of a linter to report an error in the code, not an error breaking the extension itself.
For instance, the same expression error in Javascript:
Papyrus-Lang already has a linter, the error should be properly funneling its output there similar to everything else.
Yeah. The error in question is due to the extension not properly handling the circumstance in question. The VSCode error log was posted to pastebin and linked above.
Describe the bug
Error log found here: https://pastebin.com/y81gSVYP
When the extension is attempting to read and process an expression, any time the expression is incomplete it will throw this error. It appears to "jump the gun", trying to evaluate/cast empty space.
To Reproduce
Steps to reproduce the behavior:
debug.Notification("Old Value: ")
debug.Notification("Old Value: " +)
The text was updated successfully, but these errors were encountered: