modeling-app/src/wasm-lib/kcl/tests/comparisons_multiple/execution_error.snap

---
source: kcl/src/simulation_tests.rs
description: Error from executing comparisons_multiple.kcl
---
KCL Semantic error

  × semantic: Expected a number, but found a boolean (true/false value)
   ╭────
 1 │ assert(3 == 3 == 3, "this should not compile")
   ·        ──────
   ╰────
-												Move tests into simulation (#4487)

Replace wasm-lib integration tests with KCL simulation tests.
											
										
										
											2024-11-18 16:20:32 -06:00
+								---
 								source: kcl/src/simulation_tests.rs
 								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)
 								   ╭────
 │ assert(3 == 3 == 3, "this should not compile")
 								   ·        ──────
 								   ╰────