Defect: NV-005: Malformed faker params message can echo a malformed example

[eviltester]

Parent testing issue: #1

Source defect report: https://github.com/eviltester/anywaydata-ai-testing/blob/main/docs/testing/20260625/issue-230-001/defects/NV-005-malformed-faker-params-example-echo.md
Testing artifact folder: https://github.com/eviltester/anywaydata-ai-testing/tree/main/docs/testing/20260625/issue-230-001
Original grid-table-editor story: eviltester/grid-table-editor#230
Original grid-table-editor PR: eviltester/grid-table-editor#247

The detailed defect report from the testing artifact is copied below.

---

NV-005: Malformed faker params message can echo a malformed example

Severity: Low

Status: confirmed in negative-validation lane.

Environment

• URL: https://eviltester.github.io/grid-table-editor/app.html
• Evidence: ../logs/negative-validation-test-log.md, ../screenshots/negative-07-malformed-faker-params.png

Steps to Reproduce

1. Open the deployed app and expand Test Data.
2. Select faker and choose helpers.arrayElement from the method picker.
3. Enter malformed params such as (["A","B".
4. Click Generate.

Expected Result

The validation message should explain the expected wrapping/syntax without echoing an incomplete or confusing example.

Actual Result

The UI showed: params should be wrapped in parentheses, e.g. (["A","B").

The echoed example is itself incomplete/malformed, which makes it harder for users to repair the input.

Triage Decision

I'm ok with the params example, but the issue for me is - once the user does add the extra param, they do not see an issue regarding the malformed array, instead they see Row 1: invalid faker params - Invalid Faker API Call Unsafe faker rule syntax detected: requires complex argument parsing and this makes it hard to fix, because we do not treat arrayElement as an unsafe faker rule when the array is correct so we need to report that the param needs to be an array and show an example.

[eviltester]

Implemented the triage decision in eviltester/grid-table-editor and published the branch to the test environment.

What changed:

• Kept valid helpers.arrayElement(["A", "B", "C"]) params on the safe faker path.
• Replaced the generic Unsafe faker rule syntax detected: requires complex argument parsing response for malformed/non-array array-helper params with actionable guidance.
• helpers.arrayElement(["A", "B") and helpers.arrayElement("A") now report that the helper requires an array argument and show helpers.arrayElement(["A", "B", "C"]).
• Added regression coverage at the faker runner, faker rule validator, public generation API, and shared schema row validation layers.

Commit: eviltester/grid-table-editor@1abe10c

Verification passed:

• Focused Jest for the runner/validator/API/row validation cases
• pnpm run verify:ui
• pnpm run verify:local
• Push hook verification also passed while publishing the commit

Published to test environment from branch codex/230-method-picker-mvc.
Test environment: https://eviltester.github.io/grid-table-editor/
Deploy run: https://github.com/eviltester/grid-table-editor/actions/runs/28226409039