modeling-app/rust/kcl-lib/tests/var_ref_in_own_def/ops.snap

---
source: kcl-lib/src/simulation_tests.rs
description: Operations executed var_ref_in_own_def.kcl
---
[
  {
    "type": "StdLibCall",
    "name": "startSketchOn",
    "unlabeledArg": {
      "value": {
        "type": "Plane",
        "artifact_id": "[uuid]"
      },
      "sourceRange": []
    },
    "labeledArgs": {},
    "nodePath": {
      "steps": [
        {
          "type": "ProgramBodyItem",
          "index": 0
        },
        {
          "type": "VariableDeclarationDeclaration"
        },
        {
          "type": "VariableDeclarationInit"
        },
        {
          "type": "PipeBodyItem",
          "index": 0
        }
      ]
    },
    "sourceRange": []
  }
]
KCL: Fix 'cryptic' error when referencing a variable in its own declaration (#7325) Previously, `x = cos(x)` would just say "`x` is undefined". Now it says that `x` cannot be referenced in its own definition, try using a different variable instead. To do this, I've added a new `Option<String>` field to the mod-local executor context, tracking the current variable declaration. This means cloning some strings, implying a small performance hit. I think it's fine, for the better diagnostics. In the future we could refactor this to use a &str or store variable labels in stack-allocated strings like docs.rs/compact_str or something. Closes https://github.com/KittyCAD/modeling-app/issues/6072 2025-06-02 17:25:55 -05:00			`---`
			`source: kcl-lib/src/simulation_tests.rs`
			`description: Operations executed var_ref_in_own_def.kcl`
			`---`
KCL: Better error message when using var in its own definition (#7339) I thought I did this in https://github.com/KittyCAD/modeling-app/pull/7325, but I forgot to actually set the better message. Actually fixes, for real this time, https://github.com/KittyCAD/modeling-app/issues/6072 this time. 2025-06-03 11:46:28 -05:00			`[`
			`{`
			`"type": "StdLibCall",`
			`"name": "startSketchOn",`
			`"unlabeledArg": {`
			`"value": {`
			`"type": "Plane",`
			`"artifact_id": "[uuid]"`
			`},`
			`"sourceRange": []`
			`},`
			`"labeledArgs": {},`
Change to use nodePath instead of sourceRange for Operations (#7320) * Add NodePath to operations * Change to use nodePath to get pathToNode instead of sourceRange * Add additional node path unit test * Update output * Fix import statement NodePaths * Update output * Factor into function 2025-06-05 12:24:34 -04:00			`"nodePath": {`
			`"steps": [`
			`{`
			`"type": "ProgramBodyItem",`
			`"index": 0`
			`},`
			`{`
			`"type": "VariableDeclarationDeclaration"`
			`},`
			`{`
			`"type": "VariableDeclarationInit"`
			`},`
			`{`
			`"type": "PipeBodyItem",`
			`"index": 0`
			`}`
			`]`
			`},`
KCL: Better error message when using var in its own definition (#7339) I thought I did this in https://github.com/KittyCAD/modeling-app/pull/7325, but I forgot to actually set the better message. Actually fixes, for real this time, https://github.com/KittyCAD/modeling-app/issues/6072 this time. 2025-06-03 11:46:28 -05:00			`"sourceRange": []`
			`}`
			`]`