-
Notifications
You must be signed in to change notification settings - Fork 5
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
[Bug] Regular errors are reported as "Unexpected CLI Error" despite expected failure #491
Comments
This commit makes `KipperCompileResult.warnings` always be an array even if `compileCtx` is undefined. This is to preserve cohesion with the previous bug-fix release `v0.10.3`
Fixed by #502 and will be released in the next release |
To be implemented as well for |
Uncovered edge-case discovered in Input: kipper run --target=kip --string-code=";" Result: » Unexpected CLI Error: Expected --target=kip to be one of: js, ts
» See more help with --help
» Try this: Ensure no invalid types or data were passed to module functions or classes. Otherwise report the issue
» on https://github.com/Kipper-Lang/Kipper. Help us improve Kipper! Cause: The decorator Going to be fixed with PR #510 for next release |
…ttifiedErrors()` Explanation here: #491 (comment)
Finished issue with merge of #510. |
Is there an existing issue for this?
I am following the documentation's guide
This issue exists in the latest version
Current Behavior
With the latest version
0.10.3
there is a new bug, where certain queries cause anunexpected CLI error
message.For example:
The following cmd command:
kipper run -s "x"
returns:
Expected Behavior
The failure of the command should not counted as an "Unexpected CLI Error", as it is defined behaviour.
Steps To Reproduce
0.10.3
Environment
The text was updated successfully, but these errors were encountered: