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
When compiling a program errors are only thrown with their line, column and exception name, but they do not contain any line of code displaying the origin of the error.
Example:
varx: num=4;varx: num=5;
Traceback:
Traceback:
File 'anonymous-script', line 2, col 0:
InvalidOverwriteError: Definition of variable 'x' already exists. May not overwrite existing definitions.
Expected Behavior
The traceback should contain the original line of the error.
Expected traceback:
Traceback:
File 'anonymous-script', line 2, col 0:
var x: num = 5;
^^^^^^^^^^^^^^^
InvalidOverwriteError: Definition of variable 'x' already exists. May not overwrite existing definitions.
Steps To Reproduce
Compile a program using KipperCompiler.compile() or KipperProgramContext.compileProgram() with invalid code.
Get exception using try { } catch (e) {}
Fetch traceback using e.getTraceback()
Environment
Kipper: v0.3.0
Operating System (+ Version): Windows 10 - 19043.1645
The text was updated successfully, but these errors were encountered:
Luna-Klatzer
changed the title
[BUG] Kipper Compile Errors don't display the line of code causing the error
[BUG] Missing line of origin in Kipper Errors
Apr 28, 2022
Is there an existing issue for this?
I am following the documentation's guide
This issue exists in the latest version
Current Behavior
When compiling a program errors are only thrown with their line, column and exception name, but they do not contain any line of code displaying the origin of the error.
Example:
Traceback:
Expected Behavior
The traceback should contain the original line of the error.
Expected traceback:
Steps To Reproduce
KipperCompiler.compile()
orKipperProgramContext.compileProgram()
with invalid code.try { } catch (e) {}
e.getTraceback()
Environment
The text was updated successfully, but these errors were encountered: