Parent testing issue: #1
Source defect report: https://github.com/eviltester/anywaydata-ai-testing/blob/main/docs/testing/20260625/issue-230-001/defects/AD-001-helper-arrayelement-params-unusable.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.
AD-001: helpers.arrayElement documented array params cannot be applied from the params editor
Severity: Medium
Status: confirmed repeatable in deployed test environment.
Environment
- URL: https://eviltester.github.io/grid-table-editor/generator.html
- Test environment branch/commit:
codex/230-method-picker-mvc / 04570e0e428d
- Evidence files:
../support/repeat-checks-main-agent.json, ../support/helper-arrayelement-comma-param.json, ../support/loop2-focused-rechecks.json
- Screenshots:
../screenshots/params-dialog-helpers-arrayelement.png, ../screenshots/helper-arrayelement-comma-param.png, ../screenshots/loop2-helper-arrayelement-param-dialog.png
Steps to Reproduce
- Open the deployed generator.
- In the first schema row, enter column name
Tier.
- Change field type to
faker.
- Click
Select faker command.
- Search for and apply
helpers.arrayElement.
- Click the row params/edit button.
- Try the documented/help-style array examples, for example
(["free", "pro", "enterprise"]), or a simple comma value red,green,blue.
Expected Result
The params editor should accept a valid array value or clearly explain the exact supported syntax. Applying params should allow preview/generation to choose one of the supplied values.
Actual Result
The params editor keeps Apply disabled and reports errors such as:
Row 1: invalid faker params - Invalid Faker API Call Unsafe faker rule syntax detected: requires complex argument parsing- Direct/help-style params can also produce
Cannot read properties of undefined (reading 'length').
The picker help says Params field: (["A", "B", "C"]) and Full call: helpers.arrayElement(["A", "B", "C"]), so the documented example appears unusable in the live row/params workflow.
Triaged and this is important becuase this is different from the behavior from the normal text editing where the array values can be edited so the 'unsafe' check is not applied consistently. On app.html the 'unsafe' behaviour is triggered on the ui-schema itself.
- we should show the message consistenlty
- and we should allow the 'apply' button for 'valid' but 'unsafe' because the generation and preview should be preventing the use of the unsafe, not the schema editor
- 'unsafe' is a warning in the ui editor, not a blocker
Notes
This blocks at least one required-params helper command from the method-picker-to-generator workflow and suggests structured helper params need focused review beyond this one command.
Parent testing issue: #1
Source defect report: https://github.com/eviltester/anywaydata-ai-testing/blob/main/docs/testing/20260625/issue-230-001/defects/AD-001-helper-arrayelement-params-unusable.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.
AD-001: helpers.arrayElement documented array params cannot be applied from the params editor
Severity: Medium
Status: confirmed repeatable in deployed test environment.
Environment
codex/230-method-picker-mvc/04570e0e428d../support/repeat-checks-main-agent.json,../support/helper-arrayelement-comma-param.json,../support/loop2-focused-rechecks.json../screenshots/params-dialog-helpers-arrayelement.png,../screenshots/helper-arrayelement-comma-param.png,../screenshots/loop2-helper-arrayelement-param-dialog.pngSteps to Reproduce
Tier.faker.Select faker command.helpers.arrayElement.(["free", "pro", "enterprise"]), or a simple comma valuered,green,blue.Expected Result
The params editor should accept a valid array value or clearly explain the exact supported syntax. Applying params should allow preview/generation to choose one of the supplied values.
Actual Result
The params editor keeps Apply disabled and reports errors such as:
Row 1: invalid faker params - Invalid Faker API Call Unsafe faker rule syntax detected: requires complex argument parsingCannot read properties of undefined (reading 'length').The picker help says
Params field: (["A", "B", "C"])andFull call: helpers.arrayElement(["A", "B", "C"]), so the documented example appears unusable in the live row/params workflow.Triaged and this is important becuase this is different from the behavior from the normal text editing where the array values can be edited so the 'unsafe' check is not applied consistently. On app.html the 'unsafe' behaviour is triggered on the ui-schema itself.
Notes
This blocks at least one required-params helper command from the method-picker-to-generator workflow and suggests structured helper params need focused review beyond this one command.