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

14 lines
344 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
---
transform a sketch (#5867) * transform a sketch Signed-off-by: Jess Frazelle <github@jessfraz.com> * updates Signed-off-by: Jess Frazelle <github@jessfraz.com> * fix 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! 📷🐛 * A snapshot a day keeps the bugs away! 📷🐛 * A snapshot a day keeps the bugs away! 📷🐛 * A snapshot a day keeps the bugs away! 📷🐛 * updates Signed-off-by: Jess Frazelle <github@jessfraz.com> * A snapshot a day keeps the bugs away! 📷🐛 * A snapshot a day keeps the bugs away! 📷🐛 * updates Signed-off-by: Jess Frazelle <github@jessfraz.com> --------- Signed-off-by: Jess Frazelle <github@jessfraz.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2025-03-18 16:36:48 -07: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 invalid_index_str.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
BREAKING: Change to disallow indexing KCL records/objects with strings (#6529) * Change to disallow indexing records/objects with strings * Update output * Remove outdated sim test * Fix tests
2025-04-28 12:08:47 -04:00
× semantic: Only numbers (>= 0) can be indexes
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
╭─[2:5]
1 │ arr = [1, 2, 3]
2 │ x = arr["s"]
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_index_str/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