modeling-app/rust/kcl-lib/tests/invalid_member_object/execution_error.snap

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

  × semantic: Only arrays and objects can be indexed, but you're trying to
  │ index a number
   ╭─[2:5]
 1 │ num = 999
 2 │ x = num[3]
   ·     ───┬──
   ·        ╰── tests/invalid_member_object/input.kcl
   ╰────
-												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 invalid_member_object.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: Only arrays and objects can be indexed, but you're trying to
 								  │ index a number
 								   ╭─[2:5]
 │ num = 999
 │ x = num[3]
-												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/invalid_member_object/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
+								   ╰────