ByoungSooPark/modeling-app
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
8f7ef4967f8dc30b2743cbb0ef2d28edcbba8ab4
modeling-app/rust/kcl-lib/tests/comparisons_multiple/execution_error.snap

13 lines
395 B
Plaintext
Raw Normal View History

Move tests into simulation (#4487) Replace wasm-lib integration tests with KCL simulation tests.
2024-11-18 16:20:32 -06:00
---
Kwargs: assert functions (#6406) Closes https://github.com/KittyCAD/modeling-app/issues/6408
2025-04-22 12:44:52 -05:00
source: kcl-lib/src/simulation_tests.rs
Move tests into simulation (#4487) Replace wasm-lib integration tests with KCL simulation tests.
2024-11-18 16:20:32 -06:00
description: Error from executing comparisons_multiple.kcl
---
KCL tests: take fancier snapshots of KCL errors (#4574) Right now our KCL tests output a debug representation of the KCLError value. This works OK, but it's difficult to read an error like "runtime error: SourceRange([44, 48])" because I don't fucking know what the 44th character in my KCL program is. In the modeling app, source ranges are turned into nice red squiggly underlines in the editor. I want nice squiggly underline when I run the Rust unit tests too, damnit. The JS world should NEVER have fancy toys that I, a Rust programmer, cannot access. I deserve this. I need this. So anyway instead of snapshotting debug repr, snapshot a fancy error via the miette library.
2024-11-25 17:28:57 -06:00
KCL Semantic error
× semantic: Expected a number, but found a boolean (true/false value)
╭────
Kwargs: assert functions (#6406) Closes https://github.com/KittyCAD/modeling-app/issues/6408
2025-04-22 12:44:52 -05:00
1 │ assert(3 == 3 == 3, error = "this should not compile")
better errors from rust to lsp for execution errors (#5526) * better errors start Signed-off-by: Jess Frazelle <github@jessfraz.com> * updates Signed-off-by: Jess Frazelle <github@jessfraz.com> * conversions Signed-off-by: Jess Frazelle <github@jessfraz.com> * miette update Signed-off-by: Jess Frazelle <github@jessfraz.com> * related errrors test Signed-off-by: Jess Frazelle <github@jessfraz.com> * updates Signed-off-by: Jess Frazelle <github@jessfraz.com> * a bit better Signed-off-by: Jess Frazelle <github@jessfraz.com> * updates Signed-off-by: Jess Frazelle <github@jessfraz.com> * regenerate other errors Signed-off-by: Jess Frazelle <github@jessfraz.com> * add diagnostics test Signed-off-by: Jess Frazelle <github@jessfraz.com> * updates Signed-off-by: Jess Frazelle <github@jessfraz.com> * A snapshot a day keeps the bugs away! 📷🐛 (OS: namespace-profile-ubuntu-8-cores) --------- Signed-off-by: Jess Frazelle <github@jessfraz.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2025-02-26 19:29:59 -08:00
· ───┬──
· ╰── tests/comparisons_multiple/input.kcl
KCL tests: take fancier snapshots of KCL errors (#4574) Right now our KCL tests output a debug representation of the KCLError value. This works OK, but it's difficult to read an error like "runtime error: SourceRange([44, 48])" because I don't fucking know what the 44th character in my KCL program is. In the modeling app, source ranges are turned into nice red squiggly underlines in the editor. I want nice squiggly underline when I run the Rust unit tests too, damnit. The JS world should NEVER have fancy toys that I, a Rust programmer, cannot access. I deserve this. I need this. So anyway instead of snapshotting debug repr, snapshot a fancy error via the miette library.
2024-11-25 17:28:57 -06:00
╰────
Reference in New Issue Copy Permalink