change PrepareContext to AddDataToContext, and change the data signature

[robbyt]

Previously, when passing data through to the ContextProvider, the paths were hard-coded in the final ctx object passed to the VM. This change allows customization of the final object by requiring all data is sent to the data.Provider as a map[string]any (instead of the previous non-namespaced any).

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[Copilot]

Copilot reviewed 36 out of 36 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (4)

platform/constants/ctx.go:12

• Removal of sub-key constants (e.g., Request, Response, InputData) detected. Confirm that this change is intentional and that all references now correctly use the intended string literals.

Ctx = "ctx" // top-scope variable name for accessing input data from scripts

engines/starlark/evaluator/evaluator_test.go:144

• [nitpick] Direct usage of the string literal "request" is now used instead of the previous constant. Consider extracting this key as a shared constant if consistent naming is required across the codebase.

"request": rMap,

engines/starlark/evaluator/evaluator_test.go:243

• Consider adding test cases that pass multiple input maps to verify the merging behavior of AddDataToContext.

inputs: []map[string]any{{"test": "data"}},

engines/benchmarks/benchmark_test.go:171

• [nitpick] Benchmark test now accesses the 'name' key directly instead of a nested key. Verify that this change aligns with the new convention and update any inline comments if necessary.

name := ctx["name"]

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
94.4% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud